> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/features/tips-and-hints/metric-correlation.md).

# Metric Correlation

This ability to correlate metrics greatly enhances analytical capabilities by effortlessly revealing potential relationships and patterns between separate measurements.

Metric correlation empowers users to strategically select specific metrics such as cluster or system metrics and seamlessly overlay them across essential dashboards like [Session History](/manual/features/key-features/session-history.md), [Top Queries](/manual/features/key-features/top-queries.md), and [Top Tables](/manual/features/key-features/top-tables.md).

This elevates the platform beyond conventional monitoring solutions, enabling users to delve deeper into the complexities of their PostgreSQL cluster's behavior, draw meaningful correlations, and proactively fine-tune their systems for optimal performance.

## Interactive Demo

{% @arcade/embed url="<https://app.arcade.software/share/WdBGuWxNg6zqSfRBPMAt>" flowId="WdBGuWxNg6zqSfRBPMAt" %}


---

# 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://docs.datasentinel.io/manual/features/tips-and-hints/metric-correlation.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.