> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/~/revisions/ETrLpNk6KtHjyaVUTLoE/integrations/3rd-party-metrics.md).
# 3rd-party metrics
The ability to import and display any Grafana dashboards directly into the groundcover platform offers you access to thousands of 3rd-party sources for metrics. All you need to do is to enable the scraping of custom metrics by the platform ([learn how](/~/revisions/ETrLpNk6KtHjyaVUTLoE/use-groundcover/scraping-custom-metrics.md)) and import the Grafana visualizations from a pool of over 7,000 ready-made dashboards ([see the full list](https://grafana.com/grafana/dashboards/) on Grafana's website).
Instructions on how to add each dashboard is explained in the examples below, which include some of the most popular 3rd-party sources for metrics, but the process is exactly the same for any tool.
Click any of the tools below to learn more.
---
# 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.groundcover.com/~/revisions/ETrLpNk6KtHjyaVUTLoE/integrations/3rd-party-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.
