Analytics
You need the repository's Admin role.
What's counted
Request analytics count every Maven protocol request sent through an existing repository's Maven repository URL or custom domain, whether the request came from a build, browser, or tool. This metric includes denied, invalid, not-found, and server-error responses. It differs from plan request usage, which counts authorized Maven file requests and accepted uploads. For more information, see Plans and usage.
Choose the last 24 hours, 7 days, or 30 days. Each figure is compared with the period of the same length before it.
The page shows the following:
- Requests, and the request trend over the selected period beside the figure.
- Cache hit rate: the percentage of downloads that the repository served from its stored files, without a request to an upstream. Uploads, denied requests, and not-found responses are excluded.
- Data sent and distinct client IP addresses.
- Not found: requests for files that neither the repository nor its upstreams had.
- Requests by hour or by day, stacked by outcome: cache hits, fetched from an upstream, not found, denied, uploads, and other. Point to a column, or focus the chart and use the arrow keys, to read the figures for one hour or day.
- What was requested: the most requested artifacts, each split into cache hits, fetched from an upstream, and not found, and the requested file types, such as JAR files, POM files, Maven metadata, and checksums.
- Who requested: the build tools behind the requests, whether requests were authenticated with a token or an account or were anonymous, and the countries they came from.
- Upstreams: for each upstream, the number of files fetched, the data fetched, and the average fetch duration.
Pages and API calls aren't counted. Times are in UTC.
The Storage section shows the repository's current contents: storage used and the number of files, artifacts, and versions.
How current the numbers are
Requests appear within a few minutes. At a high request rate, the counts are estimates from a sample of the requests, so the totals for a busy period can differ slightly from the exact number. The plan request count on the repository's overview page isn't sampled.