Skip to content

Dashboard And Alert Views

The GrafanaSight space dashboard is the main place to explore Grafana context inside Confluence. It shows connection status, dashboard counts, active alert counts, sync health, filters, and tabs for library and alert workflows.

GrafanaSight space dashboard library controls

Header buttons and labels:

  • Documentation opens the GrafanaSight docs.
  • Support opens Flowdence support.
  • Schedule a demo opens the demo booking page.
  • Refresh library + alerts refreshes both the dashboard catalog and active alert cache.
  • Refresh library refreshes dashboards, folders, tags, dashboard details, and panel metadata.
  • Refresh alerts refreshes active alert data only.
  • Instance shows the configured Grafana Cloud host.
  • Dashboards shows the cached dashboard count.
  • Visible alerts shows active alerts after the current filters.
  • Sync summarizes cache health.

Use the library tab to search dashboards by title, folder, tags, or alert state. The dashboard list is designed for runbook authors who need to find the right Grafana source without switching tools repeatedly.

Filters and tabs:

  • Search accepts dashboard names, tags, panel names, or alert text.
  • Folders narrows the library to selected Grafana folders.
  • Tag narrows dashboards to one Grafana tag.
  • Alert state narrows visible alert context.
  • Severity narrows alert context by severity label.
  • Library shows dashboards and dashboard detail.
  • Alerts shows cached active alerts and alert-derived macro actions.

Typical workflow:

  1. Open GrafanaSight from the Confluence space.
  2. Search for a service, system, or dashboard name.
  3. Filter by folder or tag when the library is large.
  4. Open a dashboard detail view.
  5. Inspect panels and metadata.
  6. Copy a panel or dashboard macro link into a Confluence page.

Supabase dashboard detail in GrafanaSight

Dashboard detail views include panel actions. Use View snapshot to confirm that Grafana can render the panel before inserting it into a runbook.

Supabase CPU Busy panel preview in GrafanaSight

Panel and dashboard action buttons:

  • Copy dashboard macro link copies a GrafanaSight dashboard macro URL that Confluence can auto-convert.
  • Copy panel macro link copies a GrafanaSight panel macro URL for the selected panel.
  • View snapshot fetches and displays a panel snapshot preview.
  • Refresh updates the selected dashboard or panel context.
  • Open in Grafana opens the source dashboard or panel in Grafana Cloud.

GrafanaSight loads active alert data into the space cache. Alert counts appear in the dashboard header and page byline so readers can see whether a page has active Grafana risk without opening Grafana first.

When alerts include dashboard or panel annotations, GrafanaSight can help authors copy macro links tied to the relevant visual context. This is useful for incident pages where the alert, dashboard, and action notes should stay together.

GrafanaSight alert cards and copy-link actions

Alert tab buttons and labels:

  • Copy alert summary link copies a GrafanaSight alert-summary macro link for the current alert filters.
  • Alert cards show state, severity, start time, and key labels such as folder, panel, and source.
  • Open alert source opens the alert’s source URL when Grafana provides one.
  • Copy dashboard macro link copies a dashboard macro link related to the alert.
  • Copy panel macro link copies a panel macro link related to the alert.
  • Open in Grafana opens the relevant Grafana dashboard or panel context.

The verified Supabase dashboard showed six active QA alerts and a degraded Confluence byline. The byline summarizes the current alert posture for the page while the dashboard library gives authors a place to inspect the dashboard and panel details.

Confluence page with configured GrafanaSight byline

  • Use one dashboard macro near the top of a service runbook for orientation.
  • Use detailed panel macros for the most important operational signals.
  • Use compact panel macros where a page needs quick scan density.
  • Keep alert summaries close to the remediation steps they affect.
  • Add annotations when deployments, incidents, or maintenance windows explain metric changes.