Collect MinIO Metrics Using Prometheus

Table of Contents

MinIO leverages Prometheus for metrics and alerts. MinIO publishes Prometheus-compatible scraping endpoints for cluster and node-level metrics. See Metrics for more information.

The procedure on this page documents scraping the MinIO metrics endpoints using a Prometheus instance, including deploying and configuring a simple Prometheus server for collecting metrics.

This procedure is not a replacement for the official Prometheus Documentation. Any specific guidance related to configuring, deploying, and using Prometheus is made on a best-effort basis.


Install and Configure mc with Access to the MinIO Cluster

This procedure uses mc for performing operations on the MinIO deployment. Install mc on a machine with network access to the deployment. See the mc Installation Quickstart for more complete instructions.

Prometheus Service

This procedure provides instruction for deploying Prometheus for rapid local evaluation and development. All other environments should have an existing Prometheus or Prometheus-compatible service with access to the MinIO cluster.


1) Generate the Bearer Token

MinIO by default requires authentication for requests made to the metrics endpoints. While step is not required for MinIO deployments started with MINIO_PROMETHEUS_AUTH_TYPE set to "public", you can still use the command output for retrieving a Prometheus scrape_configs entry.

Use the mc admin prometheus generate command to generate a JWT bearer token for use by Prometheus in making authenticated scraping requests:

mc admin prometheus generate ALIAS

Replace ALIAS with the alias of the MinIO deployment.

The command returns output similar to the following:

- job_name: minio-job
  bearer_token: TOKEN
  metrics_path: /minio/v2/metrics/cluster
  scheme: https
  - targets: []

The targets array can contain the hostname for any node in the deployment. For clusters with a load balancer managing connections between MinIO nodes, specify the address of the load balancer.

Specify the output block to the scrape_config section of the Prometheus configuration.

2) Configure and Run Prometheus

Follow the Prometheus Getting Started guide to download and run Prometheus locally.

Append the scrape_configs job generated in the previous step to the configuration file:

   scrape_interval: 15s

   - job_name: minio-job
     bearer_token: TOKEN
     metrics_path: /minio/v2/metrics/cluster
     scheme: https
     - targets: []

Start the Prometheus cluster using the configuration file:

prometheus --config.file=prometheus.yaml

3) Analyze Collected Metrics

Prometheus includes a expression browser. You can execute queries here to analyze the collected metrics.

The following query examples return metrics collected by Prometheus:




See Available Metrics for a complete list of published metrics.

4) Visualize Collected Metrics

The MinIO Console supports visualizing collected metrics from Prometheus. Specify the URL of the Prometheus service to the MINIO_PROMETHEUS_URL environment variable to each MinIO server in the deployment:


If you set a custom job_name for the Prometheus scraping job, you must also set MINIO_PROMETHEUS_JOB_ID to match that job name.

Restart the deployment using mc admin service restart to apply the changes.

The MinIO Console uses the metrics collected by the minio-job scraping job to populate the Dashboard metrics:

MinIO Console displaying Prometheus-backed Monitoring Data

MinIO also publishes a Grafana Dashboard for visualizing collected metrics. For more complete documentation on configuring a Prometheus data source for Grafana, see Grafana Support for Prometheus.

Prometheus includes a graphing interface for visualizing collected metrics.