# Analytics

- [Top Usage](https://docs.digma.ai/digma-developer-guide/digma-features/analytics/top-usage.md): The usage analytic allows developers to see who is using a given asset - code or non-code, and understand which areas of the app can be affected by any changes
- [Request Breakdown](https://docs.digma.ai/digma-developer-guide/digma-features/analytics/request-breakdown.md): The request
- [Duration](https://docs.digma.ai/digma-developer-guide/digma-features/analytics/duration.md): This insight provides aggregated duration statistics for the selected asset. This also includes recent changes in performance.
- [Code Nexus](https://docs.digma.ai/digma-developer-guide/digma-features/analytics/code-nexus.md): Code nexus points are areas of the code with a high level of runtime dependencies from other endpoints, services and flow. You should be watchful for change impact radius around these locations.
- [Duration Breakdown](https://docs.digma.ai/digma-developer-guide/digma-features/analytics/duration-breakdown.md): This insights allows developers to understand where how the duration of this asset is being spent among all of its child assets.  It aggregates information from all traces using the current asset.
- [Endpoint Low/High Usage](https://docs.digma.ai/digma-developer-guide/digma-features/analytics/endpoint-low-high-usage.md): This analytics provides data on actual usage of an endpoint in terms of traffic and requests per unit of time


---

# 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://docs.digma.ai/digma-developer-guide/digma-features/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.