NPMcountdy

Overview

Run several services behind Nginx Proxy Manager and sooner or later you want to know where the traffic actually goes. NPMcountdy reads the proxy's access logs and shows how much was served per domain, per path and per file, to whom, at what time of day and to which countries. The numbers stay put long after the proxy has deleted its logs.

‹›×

‹›×

‹›×

What it does

• Per domain and path. Data and requests per proxy host and per path, such as /downloads/ or /api/, plus the largest files.
• Who's downloading? Browsers, sync clients, bots and scanners are told apart by their user agent and counted separately. Everything else, such as your own apps, goes under Other.
• Countries and world map. Visitor IPs are looked up locally in the free DB-IP database. No address leaves the server.
• Time of day and responses. When the traffic happens, how much succeeded and how much stayed on the LAN.
• Survives log rotation. Hourly totals are kept for good. On first start NPMcountdy also reads logs that were already rotated, compressed ones included.
• Keeps little data. Files and visitor IPs are deleted after 90 days, and paths are cut to three levels so no individual file names end up in the database.