# HTTP Analytics

The HTTP Analytics dashboard gives a detailed view of HTTP-level activity across your CDN traffic.\
It helps you explore user interactions, identify top-performing URLs, and detect client-side or path-specific issues.\
By combining referer analysis, device statistics, and error patterns, you can optimize content delivery and improve user experience.

### Request Overview

Analyze overall request trends to understand your CDN traffic flow.

<figure><img src="/files/Q1GBAnjHsoT9sYTiyJBH" alt=""><figcaption><p>Request Overview</p></figcaption></figure>

* **Requests (time series):** Displays total requests over time.
* **Total Requests (counter):** Shows the total number of requests based on active filters.

{% hint style="info" %}
A sudden drop in request volume can indicate temporary log ingestion delay or a filtering mismatch.
{% endhint %}

### Traffic Sources

Discover where your traffic originates and which pages drive the most engagement.

<figure><img src="/files/JNuJZAJZ2YsfhZ3haAYU" alt=""><figcaption><p>Traffic Sources</p></figcaption></figure>

* **Referers (table):** Lists top referring websites or applications.
* **Paths (table):** Displays most requested URL paths (URIs).
* **Hosts (table):** Shows CDN resources generating the highest traffic.

{% hint style="info" %}
Combine **Referer** and **Status** filters to identify which external sources produce 404 or 500 errors.
{% endhint %}

### Client Insights

Break down request patterns by device type, operating system, and browser.

* **Device Types (table):** Categorizes traffic by desktop, mobile, or tablet devices.
* **OS (table):** Shows operating systems used by clients.
* **Browser (table):** Displays top browsers generating traffic.

{% hint style="info" %}
These insights help tailor optimization — for example, high mobile traffic may justify additional image compression or responsive caching rules.
{% endhint %}

### Error Behavior

Investigate HTTP errors and identify problem areas.

* **Error Patterns:** Detect 4xx or 5xx spikes and associate them with specific devices, referers, or URIs.
* **Top Error Sources:** View which domains or paths cause the highest number of failed requests.

{% hint style="warning" %}
Persistent 404 errors from the same path may indicate outdated links or incomplete content deployment on the origin.
{% endhint %}

### **Filters**

You can refine HTTP traffic analysis by applying filters to focus on specific parameters.\
All tables and charts update automatically when filters change.

<table><thead><tr><th width="279">Filter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Domain</strong></td><td>Select a specific CDN resource or host domain.</td></tr><tr><td><strong>Path</strong></td><td>Filter by URL path or partial match.</td></tr><tr><td><strong>HTTP Referer</strong></td><td>Filter by referring website or application.</td></tr><tr><td><strong>Status</strong></td><td>Filter requests by HTTP status codes (2xx–5xx).</td></tr><tr><td><strong>Metric</strong></td><td>Choose between <em>Requests</em>, <em>Data Transferred</em>, or <em>Bandwidth</em>.</td></tr></tbody></table>

{% hint style="info" %}
Use **Path** and **Referer** filters together to trace broken links or investigate referral-based performance differences.
{% endhint %}

### **FAQ**

**Why are some referers shown as “–”?**\
Requests with missing or blocked `Referer` headers (e.g., from secure contexts or privacy settings) appear as “–”.

**Can I see device-level performance metrics?**\
HTTP Analytics focuses on request and user-agent data. For latency and cache metrics, see the Performance or Cache Analytics dashboards.

**What’s the difference between Path and Host filters?**\
**Path** refers to a specific URI within a domain (e.g., `/images/banner.png`), while **Host** identifies the CDN resource or domain itself.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://clients.medianova.com/products/mn-logz/mn-logz-analytics/dashboard-library/http-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.