> 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/use-groundcover/dashboards-and-alerts/dashboard-catalog.md).

# Dashboard Catalog

## **Overview**

The Dashboard Catalog is a library of pre-built dashboards for common technologies and use cases, including Kubernetes, hosts, AWS services, databases, messaging, CI/CD, AI & LLM, and platform usage. Browse it, preview a dashboard against your own data, and install what you need in one click.

Use the filters at the top to narrow the catalog by technology or use case, for example Kubernetes, AWS, or Databases.

<figure><img src="/files/tiOlUNraIBSFI4Rn4xSZ" alt=""><figcaption><p>The Dashboard Catalog</p></figcaption></figure>

## **Installed dashboards are managed by groundcover**

There's one thing to know before you install.

An installed dashboard is **managed by groundcover and always current**. groundcover maintains its content, so when we improve a dashboard your installed copy updates automatically. You never re-install to get changes.

A managed dashboard is **read-only** and marked **Managed by groundcover** in its header. To edit it, use **Customize Dashboard**, described [below](#customize-a-dashboard).

## **Browse and preview**

1. Open the catalog from the [**Dashboards**](https://app.groundcover.com/dashboards) page.
2. Filter by category, or use **Search** to find a dashboard by name or tag. The **Recommended** filter shows the dashboards most teams start with.
3. Click a dashboard to preview it, rendered live against your own data.

<figure><img src="/files/OaakGujxnDhrCyuQN3Kf" alt=""><figcaption><p>Previewing a dashboard against live data</p></figcaption></figure>

## **Install a dashboard**

In the preview, click **Install Dashboard**. It's added to your Dashboards list and managed by groundcover. The catalog card then shows **Installed**, and **Open Dashboard** takes you to it.

<figure><img src="/files/DU7o3k8uG9mXFRusZNtt" alt=""><figcaption><p>Install Dashboard from the preview</p></figcaption></figure>

## **Customize a dashboard**

To change a managed dashboard, open it and click **Customize Dashboard**. This creates an editable copy you own, with full control over its widgets, layout, and variables.

The copy is independent and no longer tracks the catalog, so it won't receive future updates. The original managed dashboard stays in place and stays current.

<figure><img src="/files/my2oszE5BgBYcAFuMINe" alt=""><figcaption><p>Customize Dashboard on a managed dashboard</p></figcaption></figure>

## **Dashboards for your data sources**

Dashboards relevant to a connected data source are available from that data source, so you can go from a new integration to a working dashboard without browsing the full catalog.

<figure><img src="/files/pXVWVfipDHBBXcan09CR" alt=""><figcaption><p>Related dashboards from a connected data source</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/use-groundcover/dashboards-and-alerts/dashboard-catalog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
