How to Read Visitor Analytics Print

Cockpit exposes visitor analytics across the Dashboard and admin summaries so you can understand traffic volume, page activity, endpoint concentration, and how much historical data is being kept.

When to Use This

• You want to know whether the panel is seeing real traffic.
• You want to understand what the dashboard analytics widgets actually mean.
• You are checking whether analytics retention and limits are set sensibly.
• You need quick traffic context before troubleshooting a usage complaint.

Where Analytics Appear

• Dashboard: charts, country activity, endpoint concentration, long-tail endpoints, and recent activity
• Admin: visitor-day, page-view, and average-traffic summary readouts
• Settings: analytics enablement, retention days, default dashboard window, and chart limits

How to Read the Main Metrics

1. Start with total visitor and page-view style summaries to confirm traffic exists.
2. Use average visitors per day as a baseline, not an absolute performance score.
3. Check endpoint concentration to see whether a small number of routes handle most requests.
4. Use long-tail endpoint tables to spot smaller but still relevant routes.
5. Look at country and recent-activity areas when you need short-term context.

Expected Result

After reviewing Cockpit analytics, you should be able to explain whether traffic is present, which parts of the panel are busiest, and whether the current retention settings fit your needs.

What Settings Change the View

• whether visitor analytics logging is enabled at all
• how many days the dashboard shows by default
• how many endpoints are shown before the rest are grouped into other buckets
• how long analytics are retained on disk

Common Mistakes

• Assuming empty charts mean something is broken: A new install or disabled analytics setting can produce very little data.
• Ignoring retention: Short retention windows naturally reduce how much history you can see.
• Treating one spike as the whole story: Use more than one widget before drawing conclusions.

Example Use Cases

• Daily owner review: The owner checks whether traffic levels look consistent with recent days.
• Post-launch analysis: After adding new modules, the admin watches whether requests shift toward new endpoints.
• Troubleshooting: Before changing anything, the panel operator checks whether traffic is concentrated on a small number of routes.

Related Articles

• Dashboard Tour
• Settings Page Tour
• How to Review System Health Checks