Configure Grafana Enterprise Metrics
From the Grafana Helm chart point of view, the main differences between Grafana Mimir and Grafana Enterprise Metrics (GEM) are:
- GEM requires a valid license.
- Instead of using NGINX as the router of requests to internal components, GEM deploys its own enterprise gateway component that authenticates and routes requests.
- More mandatory and optional components are available, such as the admin API and various proxies.
Before you begin
Follow the instructions and Choose a name for your GEM cluster.
It is recommended, but not required to use the same name as the Helm release. For example if the cluster name is
mygem
, you’d install the chart withhelm install mygem grafana/mimir-distributed
.Follow the instruction in Get a GEM license to acquire a license.
Handling the license file
There are two options:
Provide the license as a value for the
license.contents
Helm value.Either on the command line for the
helm
command as--set-file 'license.contents=./license.jwt'
or by writing the contents into your custom values:license: contents: "iyJhbGci..."
Store the license in a Kubernetes Secret.
In this case use the following custom values:
license: external: true secretName: <name-of-your-secret>
Enable GEM in the configuration
Add the following value to your custom values:
enterprise:
enabled: true
If you want to use a different cluster name for the license and a different Helm release name on the command line, also set:
mimir:
structuredConfig:
cluster_name: <cluster-name-in-license>