Skip to content

Configuration

GrafanaSight is configured per Confluence space. A space administrator connects the space to one Grafana Cloud instance by saving the Grafana URL and service account token in the GrafanaSight configuration screen.

Empty GrafanaSight configuration screen

  1. Open the Confluence space.
  2. Open GrafanaSight configuration.
  3. Enter the Grafana Cloud URL, for example https://your-stack.grafana.net.
  4. Enter the Grafana service account token.
  5. Select Test connection.
  6. Confirm that GrafanaSight can reach Grafana and identify the organization.
  7. Select Save config.
  8. Run the first dashboard and alert load from the sync section.

GrafanaSight accepts Grafana Cloud URLs over HTTPS. It rejects non-Grafana Cloud hosts so that the app only connects to the intended Grafana Cloud service.

The configuration page is organized into connection, sync, and diagnostics sections.

Header labels:

  • Grafana identifies the configuration as a Grafana-backed space app.
  • Connected, Not configured, or an error lozenge summarizes whether the saved connection is usable.
  • Hourly sync on means background cache warming is enabled.
  • Manual sync only means admins must refresh dashboards and alerts manually.

Header buttons:

  • Schedule a demo opens the Flowdence demo booking page.
  • Documentation opens the GrafanaSight documentation.
  • Contact support opens Flowdence support.

Connection detail fields:

  • Grafana Cloud URL is the base stack URL, such as https://your-org.grafana.net.
  • Service account token is the Grafana token field. After saving, leave it blank to keep the saved token.
  • Enable hourly cache warming turns the scheduled hourly dashboard and alert refresh on or off for the space.
  • Save configuration stores the URL, token state, org data, and hourly sync setting.
  • Test connection validates the URL and token against Grafana before saving.

Sync status labels:

  • Dashboards shows cached dashboard count and last dashboard sync time.
  • Active alerts shows cached active alert count and last alert sync time.
  • Next scheduled sync shows when the hourly background job should run next when cache warming is enabled.
  • Last successful run shows the most recent successful background sync.

Sync buttons:

  • Load all dashboards and alerts runs the first full cache load after setup or token rotation.
  • Refresh dashboards refreshes dashboard catalog, folder, tag, panel, and dashboard-detail metadata.
  • Refresh alerts refreshes active alert data.
  • Reload settings rereads saved configuration and sync state from storage.

Connection diagnostics labels:

  • Org shows the Grafana organization name returned by the connection test.
  • Org ID shows the Grafana organization ID.
  • Token stored confirms whether Forge encrypted storage has a token for the space.
  • Last validated shows when the connection was last tested successfully.

GrafanaSight stores the service account token as a secret. After the token is saved, the token field stays blank on later visits. This means you can update non-secret settings without re-entering the token.

To rotate the token:

  1. Create a replacement token in Grafana Cloud.
  2. Open GrafanaSight configuration.
  3. Paste the replacement token into the token field.
  4. Test the connection.
  5. Save the configuration.
  6. Reload dashboards and alerts.

GrafanaSight caches Grafana data so Confluence pages can load quickly and so the Rovo Specialist can answer from known app data. The app maintains separate cache windows for catalog, dashboard details, panels, alerts, and annotations.

Use Load all dashboards and alerts after first configuration, after token rotation, or when you want to force a fresh space-level snapshot.

GrafanaSight configuration after a successful sync

When hourly cache warming is enabled, the gs-sync-hourly scheduled trigger refreshes the dashboard catalog and active alert cache every hour. This keeps page bylines, dashboard library search, alert macros, and Rovo Specialist answers close to current data without requiring every page view to call Grafana live.

Turn hourly cache warming off when a space should refresh only on administrator command. Manual mode does not remove saved configuration; it only stops the background cache refresh.

GrafanaSight has Forge licensing enabled. If licensing prevents app access in a tenant, users should expect Atlassian app access or subscription controls to block the GrafanaSight modules before they can use configuration, macros, bylines, or the Rovo Specialist. The configuration page remains the place to verify connection health after licensing and installation are active.

  • The Grafana URL is saved.
  • Token status shows that a token is stored.
  • Connection test succeeds.
  • Dashboard count is greater than zero for spaces with visible dashboards.
  • Alert count matches the expected active alert data.
  • The sync section shows recent activity.
  • The page byline no longer says GrafanaSight is not configured.

If connection testing fails, check the Grafana URL, token permissions, and whether the token was revoked. If dashboards load but panels do not render, confirm that Grafana rendering is available for the target dashboard and that the panel URL includes the intended dashboard UID, panel ID, and time range.