Menu

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Documentationbreadcrumb arrow Grafana Enterprise Metrics Documentationbreadcrumb arrow Manage an instancebreadcrumb arrow Using instance federation
Enterprise

Overview

GEM supports creating access policies that can span multiple instances. Doing so enables viewers in Grafana Enterprise to view data coming from more than one instance simultaneously. For example, if there were an instance called team-engineering and an instance called team-finance, an administrator might want to query metrics from both instances simultaneously.

Prerequisites

  • A configured Grafana Enterprise Metrics cluster. To create a GEM cluster, refer to Set up GEM.

  • This guide will assume there are two instances: team-engineering and team-finance. To create an instance, refer to Set up a GEM Instance.

Set up an access policy with instance federation and a token

To allow queries to span both GEM instances, which are for demonstration purposes named team-engineering and team-finance, create a new access policy called leadership. team-finance, create a new access policy called leadership. The necessary steps are:

  1. Create a new access policy leadership.

  2. Enable the Read scope.

  3. Add the instances team-engineering and team-finance.

  4. Create a new token for the access-policy and store the token in your clipboard:

Set up a Grafana data source using the access policy

  1. Create a new Prometheus data source from the Grafana configuration menu

  2. Enter the URL of your GEM cluster, ie: http://metrics-enterprise/prometheus

  3. From the Auth section, enable “Basic auth”

  4. In the User field, enter: team-engineering|team-finance where all the instance names you wish to query across are separated by the | pipe character.

  5. In the Password field, paste the token created in the token creation process.

Queries performed using this data source in either Explore or inside of dashboards will be performed across all the instances specified in the User field, and are processed as if all the data was in a single instance.