> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/developer-guide/development-cycle/dashboards.md).

# Monitor

On the Overview tab of the Monitor page, keep track of your pipelines and review execution data such as successes, failures, and performance metrics.

## **Page controls**

### **Environment and search**

Select the environment, **test** or **prod**, in the upper-left corner of the page. Then type the pipeline name in the search field to narrow the results.

### **Time period filter**

Filter pipeline execution data by time period: the last 15 minutes, 1 hour, 6 hours, 1 day, 7 days, or 30 days, or define a custom time range.

### **Percentile metrics**

Click the **See by Avg.** dropdown to select a percentile metric. This helps you identify how quickly the selected pipeline responds to requests. The chosen percentile appears on the Overview chart.

| Metric                    | Description                                                                                                                                                                                    |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Avg.** (average)        | The mean value of all executions in the selected time period. Not to be confused with the p50 metric.                                                                                          |
| **p50** (50th percentile) | The median processing time. Helps you understand the typical performance of the pipeline.                                                                                                      |
| **p90** (90th percentile) | 90% of executions had a processing time equal to or less than the displayed value.                                                                                                             |
| **p95** (95th percentile) | 95% of executions occurred below the indicated value. Useful for identifying performance degradation.                                                                                          |
| **p99** (99th percentile) | The processing time under which 99% of executions were completed. The remaining 1% are considered exceptions and may indicate more serious issues or behavior outside of the expected pattern. |

{% hint style="info" %}
Use the **Average** option for a general overview of performance, especially in scenarios with low variability. To better understand the behavior of most executions in flows with spikes or outliers, use percentiles instead.
{% endhint %}

### **Auto refresh**

Use the **Auto refresh** function to automatically update execution data at a selected interval:

* 30 seconds
* 1 minute
* 5 minutes

This option is disabled by default. To enable it, click the **Auto refresh** dropdown and select a time interval.

## **Overview chart**

In the overview chart, you can see the number of successful and failed executions, as well as the average, minimum, and maximum execution time for the pipelines shown in the table. You can also select a pipeline from the table to view only its data in the chart.

To zoom in, click and drag over the desired part of the chart. To reset the zoom, double-click the chart.

## **Overview table**

The overview table shows a summary of the executions of the most executed pipelines in the selected period. It includes:

* Pipeline name
* Pipeline version
* Total number of executions
* Errors or failed executions
* Average pipeline execution time
* [Insights](/documentation/developer-guide/development-cycle/dashboards/monitor-insights.md)

Select the **three-dot icon** at the end of each row to open the **Executions**, **Logs**, **Metrics**, or **Alerts** pages for that pipeline. These pages are already filtered to show only data relevant to the selected pipeline, making it easier to view specific information.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.digibee.com/documentation/developer-guide/development-cycle/dashboards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.