Grafana Dashboard Health Status Aggregation and Cross-Dashboard Status Sharing

Grafana Configuration
, , , ,
1

Grafana Version and Operating System:
Grafana v13.1.3 (Azure Managed Grafana)

What are you trying to achieve?
We are designing an application health monitoring dashboard with a multi-level drill-down approach:

  • L1: High-level application status overview
  • L2: Service-level health monitoring
  • L3: Resource-level monitoring under each service
  • L4: Detailed view of individual resources

The objective is to provide an overall application health view while allowing users to drill down into specific services and resources.

How are you trying to achieve it?
We are using Grafana dashboards to visualize the health and monitoring data of various application components/resources.

Each dashboard contains multiple panels representing different health indicators, metrics, and resource statuses.

What happened?
We need to understand whether the status/health information from one dashboard can be shared or consumed by another dashboard.

For example:

  • A detailed service dashboard calculates the health status based on multiple panels.
  • We want to expose the overall health status of that dashboard/service.
  • A higher-level application dashboard should consume this status to determine the overall application health.

What did you expect to happen?
We are looking for a recommended Grafana approach to share or propagate the overall dashboard/service health status to another dashboard.

The expected outcome is to avoid duplicating queries and health calculation logic across multiple dashboards and maintain a hierarchical monitoring structure.

Configuration / Scenario Details:
The complete dashboard configuration cannot be shared here due to internal implementation details.

However, the scenario is:

  • Multiple dashboards represent different monitoring layers.
  • Each lower-level dashboard determines health based on multiple panels.
  • The higher-level dashboard needs to consume the aggregated health status from the lower-level dashboards.

Did you receive any errors in Grafana UI or logs?
No errors are observed in Grafana UI or logs.

This appears to be more of a capability/architecture limitation question, and we would like to understand the recommended implementation approach.

Did you follow any online instructions?
No specific online documentation or instructions were followed for this scenario.

Question for Grafana Team:

What is the recommended Grafana-native approach to implement dashboard-to-dashboard health status sharing or aggregation?

Is there any supported mechanism to expose a dashboard/panel status as a reusable metric/value that can be consumed by another dashboard, or should this type of hierarchy be implemented using an external metric/alerting layer?

2

Grafana dashboards don’t provide a mechanism for one dashboard to consume another dashboard’s runtime-calculated panel/dashboard status as a reusable value. For this type of hierarchy, it’s better to move the health calculation into a reusable data or alerting layer rather than keeping it inside the dashboard.

Recommended approach →

Prometheus/Mimir: If the health logic can be expressed in PromQL, use a recording rule to precompute the service/resource health into a reusable time series, for example service:health_status. Dashboards at L1–L4 can then query that metric instead of duplicating the calculation. Recording-rule results can be queried by both dashboards and alert rules.

Grafana Alerting: If the desired result is an alert state, define an alert rule containing the health logic. The higher-level dashboard can display the resulting alerts with the native Alert List panel.

This gives you a common source of truth for the health calculation instead of recalculating the same logic independently in each dashboard.

If you’re using Prometheus/Mimir and the health logic can be expressed as PromQL, a recording rule is a good way to expose the calculated result as a reusable metric across the L1–L4 dashboards.

3

Hi @yagyandatta just wanted to check if you got the solution . Happy to help further if you are facing any issues .