> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/accelerate-metrics.md).
# DORA metrics
Sleuth is the most accurate and flexible way to track and improve your team's Accelerate (DORA) metrics
If you’re an engineering lead, Sleuth will make sure you have the insights you need to know how your team is performing, where they may be encountering bottlenecks and how to remove them.
A healthy team depends on trust between team and leadership. Sleuth helps you verify without breaking trust with your developers.
Sleuth's metrics experience allows you to:
* Easily understand if your performance is steady, improving or taking a turn for the worse by exploring your metrics performance for any period, with comparisons to the previous period
* Dive into actionable insights that help you spot where your projects and teams are running into bottlenecks and how to remove them
* See where your team ranks in relation to industry standards and what it will take to reach the next level
* Let the information come to you with weekly, bi-weekly or monthly email-based metrics digests and insights
* Quickly implement the tools your teams need to improve their Accelerate metrics and deployment process
---
# 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://help.sleuth.io/sleuth-dora/accelerate-metrics.md?ask=&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.
