> 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/modeling-your-deployments/organization/trends.md).

# Trends

Sleuth's **Trends** dashboard allows you spot how your initiatives (projects, labels, or teams) are trending over time.

![](https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2Favtt7QidydpaLW6I4h8T%2Fimage.png?alt=media\&token=81fa9936-bbff-405a-83ca-4f837b005f87)

You can use the date filter to see trends over the last two weeks, month, quarter or any custom date range you desire.

Each of the four DORA metrics can be drilled into to see how each metric has broken down. If your MTTR is trending up over the period use the drill-downs to discover if it's an increase in Incidents, Rollbacks or some other cause.

Using the Trends dashboard coupled with [Labels](/sleuth-dora/modeling-your-deployments/organization/labels.md) and [Teams](/sleuth-dora/modeling-your-deployments/teams.md) allows you to see trends across any taxonomy within your Organization.

{% hint style="info" %}
Trends for all projects is available on all plans. Filtering by specific projects, labels, or teams requires being on an Enterprise plan.
{% endhint %}

### How is Failure rate calculated?

Each of the four bars represents a period. For each of the 4 periods Sleuth calculates failure rate across all projects. Assume for period 3 one has three projects with corresponding failure rates

* Project A: 30%
* Project B: 0%
* Project C: 0%

The resulting average for the period is somewhere around 10%. You can see this by hovering over independent bars.

![](https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2Fmehkqi3vyYcOGppLBXrE%2Fimage.png?alt=media\&token=cb58e853-dec2-45d1-9e20-404dda831137)

The final number at the bottom represents the average across all four periods

![](https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FMJRUb9RwOGMyqoPZbGmn%2Fimage.png?alt=media\&token=7d8724dc-e835-410e-b8a7-f5267f490355)

## Further Reading

For additional information on how Sleuth calculates and "percent change" for the Trends dashboard and for other dashboards and views, see [Interpreting "Percent Change" in Sleuth](/sleuth-dora/accelerate-metrics/how-we-calculate.md#interpreting-percent-change).


---

# 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/modeling-your-deployments/organization/trends.md?ask=<question>&goal=<user_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.