Overview
Server Analytics is a live log of every request made to your site's server. Each row is one request, showing where it came from, what it hit, and how it responded, useful for debugging traffic issues, confirming a crawler or bot actually hit a page, or inspecting the exact headers a request sent.
Getting to Server Analytics
In the left sidebar, click Data.
Click Server Analytics.
Reading the log
Each row represents a single request. The table starts with the fields most useful for a quick scan:
Timestamp – when the request was made.
Host – the domain the request hit, for example www.sona.com.
Path – the specific URL path requested, for example /pricing/ or /figma/pricing-grok.svg.
Params – any query string parameters on the request, for example product=mm.
Referrer – the URL the request came from, if any.
User Agent – the browser, bot, or crawler string that made the request.
Http Code – the response status code returned, for example 200 or 301.
Additional columns
Scroll the table right to see more detail on each request:
Headers – click View Definition to open the full set of request headers as raw JSON, including fields like accept, accept-encoding, cf-connecting-ip, cf-ipcountry, cookie, referer, sec-ch-ua, and sec-fetch-mode.
IP – the IP address the request came from.
Source – where the request was served from, for example cloudflare.
Note: The Headers popup shows exactly what was sent with that request, which is useful for confirming details like the visitor's country (cf-ipcountry), the referring page (referer), or the browser/platform reported (sec-ch-ua, sec-ch-ua-platform).
Searching and filtering
Use Search path at the top of the page to find requests to a specific URL path, then click Search.
Click Filters to narrow the log down by any column instead of just path:
Every column in the table, Headers, Path, Host, Referrer, Http Code, Source, IP, Timestamp, Params, and User Agent, can be used as a filter. Use the search box inside the Filters panel to jump to a specific field instead of scrolling the list.
Click Refresh in the top-right to pull in the latest requests without reloading the page.
Paginating results
The log can hold millions of rows, so results are paginated at the bottom of the table.
Show rows – choose how many rows load per page, 25 by default.
Showing X - Y of Z – confirms your current position in the full result set, for example "Showing 1 - 25 of 2,528,227."
Previous / Next – step through pages of results.
FAQs
Does Server Analytics show every request, including bots and crawlers?
Does Server Analytics show every request, including bots and crawlers?
Yes. The log captures every request that hits the server, including browser traffic, bots, and crawlers, since it's reading at the server level rather than filtering to human visitors only.
Can I see the exact headers a specific request sent?
Can I see the exact headers a specific request sent?
Yes. Click View Definition in the Headers column for any row to see the full raw header set for that request.
Why would a request show an Http Code of 301 instead of 200?
Why would a request show an Http Code of 301 instead of 200?
A 301 means that request was redirected, for example from a bare domain to www., rather than served directly. A 200 means the request was served successfully.
Can I filter by more than one field at once?
Can I filter by more than one field at once?
Open Filters and select the fields you want; each one you add narrows the log further, so you can combine filters like Host and Http Code together.
How much history does the log keep?
How much history does the log keep?
The exact retention window can vary. If you need data older than what's currently showing, check with your workspace admin or contact support to confirm how far back the log goes.