Dashboard & analytics
Admin guide
Dashboard & analytics
The admin dashboard turns your node's traffic into charts you can actually read — no separate analytics service, no external tracking, no cookies. Data comes straight from the app's own tables (users, publications, engagements, follows, sessions, federation messages).
What's on the dashboard
Stat cards (live counts):
- Members
- Posts
- Engagement (likes/comments/reactions)
- Follows
- Communities
- Active sessions (last 24h)
- Open reports
- Pending federation (queued inbound)
Charts with 7 / 14 / 30-day filters:
- New members — registrations per day
- Posts & engagement — publications, engagement, follows over time
- Active sessions — site traffic per day
- Fediverse activity — inbound vs outbound federation messages per day
Why this matters
The dashboard is a health check, not just vanity metrics:
- A spike in open reports → check Moderation.
- A growing pending federation count → check the queue worker/cron and
fedifuel:consume-inbound. - Active sessions tracking away from signups → onboarding or engagement issue.
- Fediverse activity shows whether federation is actually flowing both ways.
Data privacy
All aggregation happens locally on your node. No third party, no analytics cookie, no data leaving your server.
Federation status
php artisan federation:statusprints the active driver and local-actor stats.- The Fediverse activity chart on the dashboard reflects real inbound/outbound
message volume from
social_federation_messages.
Related
Still stuck? Contact the node administrator.