This is archived documentation for v2.0.x. Go to the latest version.

Grafana Mimir migration guidesMigrating from Cortex to Grafana Mimir

Migrating from Cortex to Grafana Mimir

This document guides an operator through the process of migrating a deployment of Cortex to Grafana Mimir. It includes an overview of the steps required for any environment and specific instructions for environments deployed with Jsonnet.

Grafana Mimir 2.0.0 includes significant changes that simplify the deployment and continued operation of a horizontally scalable, multi-tenant time series database with long-term storage.

The changes focus on making Grafana Mimir easier to run out of the box, including:

  • Removing configuration parameters that don’t require tuning
  • Renaming some parameters so that they’re more easily understood
  • Updating the default values of some existing parameters

The mimirtool automates configuration conversion. It provides a simple migration by generating Mimir configuration from Cortex configuration.

Before you begin

  • Ensure that you are running either Cortex 1.10.X or Cortex 1.11.X.

    If you are running an older version of Cortex, upgrade to 1.11.1 before proceeding with the migration.

  • Ensure you have installed Cortex alerting and recording rules as well as Cortex dashboards.

    The monitoring mixin has both alerting and recording rules to install in either Prometheus or Cortex as well as dashboards to install in Grafana. To download a prebuilt ZIP file that contains the alerting and recording rules, refer to Release Cortex-jsonnet 1.11.1.

    To upload rules to the ruler using mimirtool, refer to mimirtool rules. To import the dashboards into Grafana, refer to Import dashboard.

Notable changes

Note: For full list of changes, refer to the project CHANGELOG.

  • The Grafana Mimir HTTP server defaults to listening on port 8080; Cortex defaults to listening on port 80. To maintain port 80 as the listening port, set -server.http-listen-port=80.

  • Grafana Mimir uses anonymous as the default tenant ID when -auth.multitenancy=false. Cortex uses fake as the default tenant ID when -auth.enabled=false. Use -auth.no-auth-tenant=fake when -auth.multitenancy=false to match the Cortex default tenant ID.

  • Grafana Mimir removes the legacy HTTP prefixes deprecated in Cortex.

    • Query endpoints

      LegacyCurrent
      /<legacy-http-prefix>/api/v1/query<prometheus-http-prefix>/api/v1/query
      /<legacy-http-prefix>/api/v1/query_range<prometheus-http-prefix>/api/v1/query_range
      /<legacy-http-prefix>/api/v1/query_exemplars<prometheus-http-prefix>/api/v1/query_exemplars
      /<legacy-http-prefix>/api/v1/series<prometheus-http-prefix>/api/v1/series
      /<legacy-http-prefix>/api/v1/labels<prometheus-http-prefix>/api/v1/labels
      /<legacy-http-prefix>/api/v1/label/{name}/values<prometheus-http-prefix>/api/v1/label/{name}/values
      /<legacy-http-prefix>/api/v1/metadata<prometheus-http-prefix>/api/v1/metadata
      /<legacy-http-prefix>/api/v1/read<prometheus-http-prefix>/api/v1/read
      /<legacy-http-prefix>/api/v1/cardinality/label_names<prometheus-http-prefix>/api/v1/cardinality/label_names
      /<legacy-http-prefix>/api/v1/cardinality/label_values<prometheus-http-prefix>/api/v1/cardinality/label_values
      /api/prom/user_stats/api/v1/user_stats
    • Distributor endpoints

      Legacy endpointCurrent
      /<legacy-http-prefix>/push/api/v1/push
      /all_user_stats/distributor/all_user_stats
      /ha-tracker/distributor/ha_tracker
    • Ingester endpoints

      LegacyCurrent
      /ring/ingester/ring
      /shutdown/ingester/shutdown
      /flush/ingester/flush
      /push/ingester/push
    • Ruler endpoints

      LegacyCurrent
      /<legacy-http-prefix>/api/v1/rules<prometheus-http-prefix>/api/v1/rules
      /<legacy-http-prefix>/api/v1/alerts<prometheus-http-prefix>/api/v1/alerts
      /<legacy-http-prefix>/rules/api/v1/rules (see below)
      /<legacy-http-prefix>/rules/{namespace}/api/v1/rules/{namespace} (see below)
      /<legacy-http-prefix>/rules/{namespace}/{groupName}/api/v1/rules/{namespace}/{groupName} (see below)
      /<legacy-http-prefix>/rules/{namespace}/api/v1/rules/{namespace} (see below)
      /<legacy-http-prefix>/rules/{namespace}/{groupName}/api/v1/rules/{namespace}/{groupName} (see below)
      /<legacy-http-prefix>/rules/{namespace}/api/v1/rules/{namespace} (see below)
      /ruler_ring/ruler/ring

      Note: The /api/v1/rules/** endpoints are considered deprecated with Mimir 2.0.0 and will be removed in Mimir 2.2.0. After upgrading to 2.0.0 we recommend switching uses to the equivalent /<prometheus-http-prefix>/config/v1/** endpoints that Mimir 2.0.0 introduces.

    • Alertmanager endpoints

      LegacyCurrent
      /<legacy-http-prefix>/alertmanager
      /status/multitenant_alertmanager/status

Generating configuration for Grafana Mimir

mimirtool provides a command for converting Cortex configuration to Mimir configuration that you can use to update both flags and configuration files.

Download mimirtool

Download the appropriate release asset for your operating system and architecture and make it executable. For Linux with the AMD64 architecture:

curl -fLo mimirtool https://github.com/grafana/mimir/releases/latest/download/mimirtool-linux-amd64
chmod +x mimirtool

Use mimirtool

The mimirtool config convert command converts Cortex 1.11 configuration files to Grafana Mimir 2.0 configuration files. It removes any configuration parameters that are no longer available in Grafana Mimir, and it renames configuration parameters that have a new name. If you have explicitly set configuration parameters to a value matching the Cortex default, by default, mimirtool config convert doesn’t update the value. To have mimirtool config convert update explicitly set values from the Cortex defaults to the new Grafana Mimir defaults, provide the --update-defaults flag. Refer to convert for more information on using mimirtool for configuration conversion.

Updating to Grafana Mimir using Jsonnet

Grafana Mimir has a Jsonnet library that replaces the existing Cortex Jsonnet library and updated monitoring mixin.

Migrate to Grafana Mimir video

The following video shows you how to migrate to Grafana Mimir using Jsonnet.


Migrate to Grafana Mimir instructions

The following instructions describe how to migrate to Grafana Mimir using Jsonnet.

To install the updated libraries using jsonnet-bundler, run the following commands:

jb install github.com/grafana/mimir/operations/mimir@main
jb install github.com/grafana/mimir/operations/mimir-mixin@main

To deploy the updated Jsonnet:

  1. Install the updated monitoring mixin.

    a. Add the dashboards to Grafana. The dashboards replace your Cortex dashboards and continue to work for monitoring Cortex deployments.

    Note: Resource dashboards are now enabled by default and require additional metrics sources. To understand the required metrics sources, refer to Additional resources metrics.

    b. Install the recording and alerting rules into the ruler or a Prometheus server.

  2. Replace the import of the Cortex Jsonnet library with the Mimir Jsonnet library. For example:

    import 'github.com/grafana/mimir/operations/mimir/mimir.libsonnet'
    
  3. Remove the cortex_ prefix from any member keys of the <MIMIR>._config object. For example, cortex_compactor_disk_data_size becomes compactor_disk_data_size.

  4. If you are using the Cortex defaults, set the server HTTP port to 80. The new Mimir default is 8080. For example:

    (import 'github.com/grafana/mimir/operations/mimir/mimir.libsonnet') {
      _config+: {
        server_http.port: 80,
      },
    }
    
  5. For each component, use mimirtool to update the configured arguments. To extract the flags for each component, refer to Extracting flags from Jsonnet.

  6. Apply the updated Jsonnet

To verify that the cluster is operating correctly, use the monitoring mixin dashboards.

Updating to Grafana Mimir using Helm

You can update to the Grafana Mimir Helm chart from the Cortex Helm chart.

Before you begin

  • Ensure that you are running the v1.4.0 release of the Cortex Helm chart.

  • Ensure that you are running ingesters using a Kubernetes StatefulSet.

    In the values.yaml file:

    ingester:
      statefulSet:
        enabled: true
    

To migrate to the Grafana Mimir Helm chart:

  1. Install the updated monitoring mixin.

    a. Add the dashboards to Grafana. The dashboards replace your Cortex dashboards and continue to work for monitoring Cortex deployments.

    Note: Resource dashboards are now enabled by default and require additional metrics sources. To understand the required metrics sources, refer to Additional resources metrics.

    b. Install the recording and alerting rules into the ruler or a Prometheus server.

  2. Run the following command to add the Grafana Helm chart repository:

    helm repo add grafana https://grafana.github.io/helm-charts
    
  3. Convert the Cortex configuration in your values.yaml file.

    a. Extract the Cortex configuration and write the output to the cortex.yaml file.

    yq -Y '.config' <VALUES YAML FILE> > cortex.yaml
    

    b. Use mimirtool to update the configuration.

    mimirtool config convert cortex.yaml
    

    c. Place the updated configuration under the mimir.config key at the top level of your Helm values file.

    Note: The Grafana Mimir Helm chart expects the configuration as a string value. You can provide a literal block string with the | symbol.

    In your Helm values file:

    mimir:
      config: |
        <CONFIGURATION FILE CONTENTS>
    

    d. Merge the templated configuration from the mimir-distributed values.yaml file. The Cortex Helm chart sets some additional configuration using flags. The Grafana Mimir Helm chart sets that additional configuration in the configuration file.

    • Set frontend_worker.frontend_address to '{{ template "mimir.fullname" . }}-query-frontend-headless.{{ .Release.Namespace }}.svc:{{ include "mimir.serverGrpcListenPort" . }}'.
    • Set ruler.alertmanager_url to 'dnssrvnoa+http://_http-metrics._tcp.{{ template "mimir.fullname" . }}-alertmanager-headless.{{ .Release.Namespace }}.svc.cluster.local/alertmanager'.
    • If you want to use memberlist as the ring KV store, set memberlist.join_members to ['{{ include "mimir.fullname" . }}-gossip-ring'].
    • Append the caching configuration to blocks_storage.bucket_store.

    A partial Helm values file with the changes incorporated looks similar to:

    mimir:
      config: |
        blocks_storage:
          {{- if .Values.memcached.enabled }}
          chunks_cache:
            backend: "memcached"
            memcached:
              addresses: "dns+{{ .Release.Name }}-memcached.{{ .Release.Namespace }}.svc:11211"
              max_item_size: {{ .Values.memcached.maxItemMemory }}
          {{- end }}
          {{- if index .Values "memcached-metadata" "enabled" }}
          metadata_cache:
            backend: "memcached"
            memcached:
              addresses: "dns+{{ .Release.Name }}-memcached-metadata.{{ .Release.Namespace }}.svc:11211"
              max_item_size: {{ (index .Values "memcached-metadata").maxItemMemory }}
          {{- end }}
          {{- if index .Values "memcached-queries" "enabled" }}
          index_cache:
            backend: "memcached"
            memcached:
              addresses: "dns+{{ .Release.Name }}-memcached-queries.{{ .Release.Namespace }}.svc:11211"
              max_item_size: {{ (index .Values "memcached-queries").maxItemMemory }}
          {{- end }}
        frontend_worker:
          frontend_address: "{{ template "mimir.fullname" . }}-query-frontend-headless.{{ .Release.Namespace }}.svc:{{ include "mimir.serverGrpcListenPort" . }}"
        memberlist:
          join_members: ["{{ include "mimir.fullname" . }}-gossip-ring"]
        ruler:
          alertmanager_url: "dnssrvnoa+http://_http-metrics._tcp.{{ template "mimir.fullname" . }}-alertmanager-headless.{{ .Release.Namespace }}.svc.cluster.local/alertmanager"
    

    e. Remove the original Cortex $.config member.

    Note: The $ symbol refers to the top level of the values file.

    f. Set the ingester podManagementPolicy to "OrderedReady". The Grafana Mimir chart prefers "Parallel" for faster scale up, but this field is immutable on an existing StatefulSet.

    In your values.yaml file:

    ingester:
      podManagementPolicy: "OrderedReady"
    

    g. Set the nameOverride to cortex. This configuration parameter ensures that resources have the same names as those created by the Cortex Helm chart and ensures Kubernetes performs a rolling upgrade of existing resources instead of creating new resources.

    In your values.yaml file:

    nameOverride: "cortex"
    

    h. Disable MinIO. The Grafana Mimir Helm chart enables MinIO by default for convenience during first time installs. If you are migrating from Cortex, use your existing object storage, and disable MinIO.

    In your values.yaml file:

    minio:
      enabled: false
    
  4. Run the Helm upgrade with the Grafana Mimir chart.

    Note: The name of the release must match your Cortex Helm chart release.

    helm upgrade <RELEASE> grafana/mimir [-n <NAMESPACE>]
    

To verify that the cluster is operating correctly, use the monitoring mixin dashboards.