# Digma Features

- [Issues](https://docs.digma.ai/digma-developer-guide/digma-features/insights.md)
- [Suspected N+1](https://docs.digma.ai/digma-developer-guide/digma-features/insights/suspected-n+1.md): N+1 queries are usually a result of modeling issues created by ORMs. They manifest in an excessive number of queries that can carry a performance cost.
- [Excessive API calls (chatty API)](https://docs.digma.ai/digma-developer-guide/digma-features/insights/excessive-api-calls-chatty-api.md): Digma can detect situations of excessive API chatter between different microservices or to different APIs and point them out.
- [Bottleneck](https://docs.digma.ai/digma-developer-guide/digma-features/insights/bottleneck.md): This insight identifies assets that hold up requests by taking a large portion of their time. An asset will not be considered a bottleneck if it is a part of a non-blocking asynchronous execution.
- [Scaling Issue](https://docs.digma.ai/digma-developer-guide/digma-features/insights/scaling-issue.md): The scaling issue insight analyzes how the code performs when running concurrently and automatically tries to RCA the cause of any performance issues.
- [Session In View Query Detected](https://docs.digma.ai/digma-developer-guide/digma-features/insights/session-in-view-query-detected.md): Open Session in View is a common anti-pattern in which the database session is left open during view rendering, possibly resulting in lazy database queries at the rendering phase.
- [Query Optimization Suggested](https://docs.digma.ai/digma-developer-guide/digma-features/insights/query-optimization-suggested.md): This insight identifies queries that are abnormally  slow and are considered candidates for optimization
- [High number of queries](https://docs.digma.ai/digma-developer-guide/digma-features/insights/high-number-of-queries.md): This insight identifies endpoints that trigger an abnormal amount of queries. This can be caused by abstraction issues or not using bulk queries when applicable
- [Slow Endpoint](https://docs.digma.ai/digma-developer-guide/digma-features/insights/slow-endpoint.md): This insight provides an indication if a particular endpoint is slower than others by a substantial degree
- [Analytics](https://docs.digma.ai/digma-developer-guide/digma-features/analytics.md)
- [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
- [Performance Impact](https://docs.digma.ai/digma-developer-guide/digma-features/performance-impact.md)
- [Test observability](https://docs.digma.ai/digma-developer-guide/digma-features/test-observability.md)
- [Issue Criticality](https://docs.digma.ai/digma-developer-guide/digma-features/criticality.md)


---

# 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.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.