DumbMonit
IntegrationsStorage and backups
Monitor MinIO with DumbMonit
BetaA MinIO object store through its Prometheus metrics: nodes and drives offline, capacity, failed heals, replication failures and S3 server errors.
DocumentationOfficial website: MinIO
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
This integration was built from the MinIO metrics documentation, not against a running server yet. It only reads. Tell us what breaks. A MinIO object store through its Prometheus metrics: nodes and drives that went offline, raw and usable capacity, objects and buckets, the self-healing that fails, replication failures and S3 requests that end in a server error.
Typical use. Object store (beta): nodes and drives offline, capacity, heal and replication failures, S3 errors
Examples
- MinIO single node
- MinIO distributed cluster
How it connects
What you need
- Prometheus tokenThe bearer_token printed by mc admin prometheus generate. It opens the metrics pages only.
No account needed.
Network ports to open
9000/TCPS3 API and metrics (HTTP or HTTPS, default)
Setup steps: Generate a Prometheus token for DumbMonit
With the mc client configured for your MinIO (alias myminio), generate the token of the cluster metrics.
mc admin prometheus generate myminio clusterCopy the value after bearer_token in the output: that is the token.
In DumbMonit, enter the MinIO address (for example minio.lan), paste the token as Prometheus token and choose https if MinIO serves TLS.
Heads-up. The token only opens the metrics pages, but anyone holding it can read them. If MinIO runs with MINIO_PROMETHEUS_AUTH_TYPE=public, the metrics need no token: choose No authentication.