# Analytics

Analytics offers insights into the performance of Aviator and provides metrics on its usage. The following metrics are offered on the Analytics page of Aviator.

## **Time in Queue**

The time a PR spends in the queue before it is merged by the Aviator bot. The time is measured starting when the PR is queued (not labeled). This only includes the PRs that were merged by the Aviator bot. The metric is reported as: Average, p50 (50th percentile), p75 (75th percentile), p90 (90th percentile) and p100 (100th percentile).

![](https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FR9g50axgyirVgVfajskI%2FScreen%20Shot%202022-05-17%20at%203.36.03%20PM.png?alt=media\&token=c02567af-be69-49a9-84b4-69baadf88131)

## Aviator **bot usage**

Represents how many PRs were merged by the bot vs. merged manually segmented by day.

## **PR failure reasons**

Gives you a better understanding of how many PRs are failing to automatically merge and why. The breakdown is done by Failure reasons. You can find more details in the [<mark style="color:blue;">Error Codes</mark>](https://docs.aviator.co/mergequeue/reference/status-codes) section.

The failed PR is counted multiple times if it failed multiple times in its lifecycle.

## **PR sync frequency**

This metric captures how many times the bot pulls the latest base branch into the current PR. This should only happen at most once if everyone uses the Aviator bot for merging the PRs.

## Learn More

* [<mark style="color:blue;">Analytics API documentation</mark>](https://docs.aviator.co/api)

## See Also

* [Monitoring Metrics](https://docs.aviator.co/api/reference/monitoring-metrics) for Prometheus metrics


---

# 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.aviator.co/mergequeue/concepts/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.