Activity
See how many logs and HTTP requests a project receives, on which routes, and at which hours.
This page shows you how to read a project's activity: logs over time by level, HTTP requests by status, the busiest routes, and the hours of the week when most happens.
Where to find it
Open a project. Once its first log has arrived, the overview starts with Activity. Choose a range: the last 24 hours, 7 days (the default), 30 days or 90 days. Every role can see it.
Logs
Every log the project receives counts once, at its level: debug (which includes trace), info, warn, error and fatal. That includes trace and debug lines, which dlogify does not keep otherwise. The 24-hour and 7-day ranges show one bar per hour in UTC; the 30-day and 90-day ranges show one bar per day in the project's timezone.
Each log counts in the hour it happened, from its own timestamp, not when it arrived. A log dated more than 90 days back, which would fall outside what is kept, counts in the hour it arrived. Counts appear a few seconds after the logs are sent.
Requests
A request is an HTTP access log: a log with http.request.method, http.response.status_code, and one of http.route, logify.http.router or url.path, whatever produced it: your application, nginx, Envoy, Traefik through the collector preset or another proxy. A log about an outgoing call (with url.full instead of a route or path) and an error log with a stack trace or exception are not requests.
Requests are shown by status class (2xx, 3xx, 4xx, 5xx) with the share of 5xx responses. 1xx responses count in the total only. If the project sends no access logs, this chart is replaced by a note.
Top routes
The busiest routes of the range, by requests or by 5xx responses. A route is the method with http.route, else logify.http.router, else (unmatched) when only the concrete path was reported. dlogify keeps up to 200 routes per project and hour; requests to further routes in that hour count under (other).
When activity happens
A grid of the last 7 or 30 days, one row per weekday and one column per hour, in the project's timezone. Brighter cells had more logs per hour (the Less–More legend shows the steps); hover a cell to see its total, its levels and its requests. Thirty days are not whole weeks, so two weekdays occur five times instead of four; cells are coloured by their average per hour, so those days do not look busier than they were. Set the timezone in the project's notification settings.
Hours are counted in UTC and placed in the local hour in which they start, so in a timezone with a half-hour offset (such as India, UTC+05:30) a cell covers the UTC hour that starts in that local hour.
How long it is kept
Activity is kept 90 days on every plan. It starts counting when this feature was released; earlier logs are not included.