0 3 * * * = 3 AM daily | 0 */6 * * * = every 6 hours0 8 1 * * = 8 AM on the 1st of each month/admin matches /admin/login etc.daily_ips table — each distinct IP address is counted once across the entire reporting period, regardless of how many days they visited. This avoids the inflation caused by summing per-day unique counts.
returning IPs / total unique IPs × 100.
daily_pages table. Only human requests (non-bot) to actual page paths are counted — assets like CSS, JS, images, fonts, PDFs, and known server-side scripts are excluded. Error responses (4xx/5xx) are subtracted from the count. If GA4 or a client-side tracker is connected, those more accurate numbers are used instead.
bytes column in daily_stats. Displayed in human-readable format (KB, MB, GB).
daily_stats table. Bot traffic is excluded. Each bar represents one day's total human request count.
referrer field in requests. Self-referrals (same domain) and internal/dev hosts are excluded. Percentages are relative to the top 10 external referrers shown.
data/geo_cache.db). Private IPs and known bot ranges are excluded. If IP resolution fails entirely, this section is hidden.
utm_source, utm_medium, utm_campaign) are parsed from request query strings. This section only appears when campaign-tagged traffic is detected. Campaign doughnut, source bar chart, and channel distribution are all derived from UTM parameters.
/wp-*, /images/, /robots.txt, /ads.txt, etc.) are excluded. Only appears when search engine crawl data exists.
pip install google-auth google-analytics-data
logdash-analytics123456789).
| Site | GA4 Property ID | Status | Actions |
|---|
Downloads a ZIP file containing:
Database files (.db) are not included — they re-import automatically from your log servers.
Upload a previously downloaded backup ZIP to restore your configuration.
⚠️ This will overwrite your current settings. A timestamped backup of existing files is created automatically before overwriting.
logdash_deploy_full_vXX.zip (full) or logdash_patch_vXX.zip (patch)Full deploy — contains app/ and frontend/ directories. Backs up the existing install, then replaces all files. Use for clean installs or major upgrades.
Patch deploy — contains only changed files. Overlays on top of the existing install without touching other files. Use for incremental updates.
The deploy runs logdash-redeploy.sh on the server. The service will restart automatically. Expect a few seconds of downtime during restart.
/{site}/bennielong (was going to standard report)/{site}/benniechopliver