> For the complete documentation index, see [llms.txt](https://docs.dashboard.devtron.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dashboard.devtron.ai/user-guide/resource-browser/monitoring-graphs.md).

# Add Monitoring Dashboards/Graphs

## Introduction [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)

The Resource Browser allows you to integrate monitoring graphs and dashboards from tools like Grafana, Kibana, Prometheus, and many more tools, with each cluster. This centralizes all monitoring visuals for your clusters in one place within Devtron, streamlining troubleshooting and significantly reducing manual effort.

It works similarly to a 'Single Pane of Glass (SPOG)' that displays data coming from different sources in a single unified view.

![Adding Monitoring Visualizations](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/kubernetes-resource-browser/monitoring-graphs.gif)

***

## Tutorial

{% embed url="<https://www.youtube.com/watch?v=XHfrAsHhTQ0>" %}

***

## Steps

1. Go to **Resource Browser** and select your cluster.
2. Click the graph icon as shown below and click the **Add Panel** button.

   ![Adding Monitoring](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/kubernetes-resource-browser/add-graph1.jpg)
3. Give a name to the monitoring dashboard and add the `iframe` code supplied by your graph/dashboard tool.

   ![Adding Monitoring](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/kubernetes-resource-browser/fields-filled.jpg)
4. Click **Save**.

You can also rearrange and resize the graphs/dashboards in case you have added many of them. Refer the [tutorial](#tutorial) to know 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.dashboard.devtron.ai/user-guide/resource-browser/monitoring-graphs.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.