> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/grafana-dashboards.md).

# Grafana Dashboards

## Where the links are

<table><thead><tr><th width="290">Location</th><th>Links</th></tr></thead><tbody><tr><td><a href="/pages/HnYiEFXDUSkrkEMGk1bT">Validators list</a></td><td><strong>Metrics</strong> and <strong>Logs</strong> columns, per validator, targeting its participant.</td></tr><tr><td><a href="/pages/jhTEnSFdrHJF9o1DUx3s">Validator → Summary</a></td><td>Per component row: metrics for the participant, logs for every component.</td></tr><tr><td><a href="/pages/tcGQBtcrXgXB7kA5XoKs">Applications list</a></td><td><strong>Metrics</strong> and <strong>Logs</strong> columns per application.</td></tr><tr><td><a href="/spaces/ZLShxGrGwfiYOlD144KQ/pages/zTObaUS5UwjZl5GeO4ZH">Application details</a></td><td><strong>Open in Grafana</strong> links in the <strong>Endpoints</strong> section.</td></tr></tbody></table>

All of them open in a new tab, so you keep your place in the console.

## What each link opens

**Logs** opens Grafana's Loki log explorer, filtered to the component's service name, over the **last 24 hours**, newest first.

**Metrics** opens the Canton participant dashboard, filtered to that participant, over the **last hour**, refreshing every five minutes.

{% hint style="info" %}
**Metrics links only appear for participant components.** The participant is the component with a Canton-specific dashboard; other components expose standard Kubernetes workload metrics, which you can reach through your own dashboards. Logs are available for every component.
{% endhint %}

## Configuration

Set at install time, in the Helm values:

<table><thead><tr><th width="260">Value</th><th>Purpose</th></tr></thead><tbody><tr><td><code>ui.grafana.baseUrl</code></td><td>Base URL of your Grafana instance.</td></tr><tr><td><code>ui.grafana.dataSource</code></td><td>Optional. The UID of the Loki data source to query, when Grafana has more than one.</td></tr></tbody></table>

{% hint style="warning" %}
**The Grafana buttons are always rendered**, whether or not `ui.grafana.baseUrl` points at a reachable Grafana. If you have not configured it, the links will open a broken page rather than being hidden. Set `ui.grafana.baseUrl` as part of every install.
{% endhint %}

## Prerequisites

For these links to resolve to real data you need:

* **Grafana**, reachable by the people using the console.
* **Loki**, receiving logs from the cluster, for the log links.
* **Prometheus**, scraping validator component metrics, for the metrics links. Enable `monitoring.serviceMonitor.enabled` in the Helm values if you use the Prometheus Operator.
* **The Canton participant dashboard** installed in your Grafana. Contact IntellectEU support for the dashboard definition.

{% hint style="info" %}
The resource figures shown *inside* the console — the CPU and memory bars on the lists and detail pages — do not come from Prometheus. They come from the Kubernetes metrics API, which requires `metrics-server` in the cluster. Prometheus and Grafana are only needed for the deep links.
{% endhint %}


---

# 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.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/grafana-dashboards.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.