DumbMonit
ИнтеграцииХранилища и резервные копии
Мониторинг MinIO в DumbMonit
БетаA MinIO object store through its Prometheus metrics: nodes and drives offline, capacity, failed heals, replication failures and S3 server errors.
ДокументацияОфициальный сайт: MinIO
Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.
Что проверяет DumbMonit
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.
Типичное применение. Object store (beta): nodes and drives offline, capacity, heal and replication failures, S3 errors
Примеры
- MinIO single node
- MinIO distributed cluster
Как подключается
Что понадобится
- Prometheus tokenThe bearer_token printed by mc admin prometheus generate. It opens the metrics pages only.
Учётная запись не нужна.
Сетевые порты, которые нужно открыть
9000/TCPS3 API and metrics (HTTP or HTTPS, default)
Шаги настройки: 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.
Обратите внимание. 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.