> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/edgesight/analytics/your-dashboards/bot-analytics.md).

# Bot Analytics

Analyze automated and bot-generated CDN traffic by request volume, country, user agent, and HTTP status.

The **Bot Analytics** dashboard provides a detailed view of automated and bot-generated traffic across your CDN.

Use this dashboard to identify bots accessing your services, analyze where bot requests originate, and review how frequently different bots interact with your content. Bot traffic can be evaluated using request volume, country, user agent, HTTP status, and related traffic data.

## Bot Request Overview

Review bot-generated request volume over the selected time range.

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

These metrics provide an overview of automated traffic and help identify changes in bot request volume.

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2Fin7ByjWWpHddA8XAfOQ9%2Fimage.png?alt=media&amp;token=16f01d11-513d-4630-9a2a-ce5910452fea" alt=""><figcaption></figcaption></figure>

## Bot Country Distribution

Analyze the geographic distribution of bot-generated traffic.

* **Country Distribution of Bots:** Shows the distribution of bot requests by country.
* **Country Distribution of User Agents:** Shows the countries associated with bot user agents.

Use these visualizations to identify where automated requests originate and compare the geographic activity of different bot user agents.

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2FSoaJXls9CTXqGz9V0ha6%2Fimage.png?alt=media&amp;token=063df7b4-f8ae-4bc3-973c-af8f292ec4ce" alt=""><figcaption></figcaption></figure>

## Analyze Bot Traffic

Bot Analytics can help you evaluate automated traffic before configuring user-agent-based access controls.

For example, you can use the dashboard to:

* Identify user agents generating automated traffic.
* Review request volume and geographic distribution for detected bots.
* Analyze HTTP status codes associated with bot requests.
* Identify unusual or potentially unwanted bot activity.
* Review bot traffic before deciding whether a user agent should be allowed or blocked.

{% hint style="info" %}
Review bot traffic patterns before applying user-agent-based blocking rules. This can help distinguish unwanted automated traffic from legitimate bots that may be required for your services.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/edgesight/analytics/your-dashboards/bot-analytics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.