DumbMonit

ИнтеграцииБазы данных и очереди сообщений

Мониторинг Elasticsearch / OpenSearch в DumbMonit

The search cluster: red or yellow status, unassigned shards, disk filling up on a node and JVM heap pressure.

ДокументацияОфициальный сайт: Elasticsearch

Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.

Что проверяет DumbMonit

Elasticsearch and OpenSearch: cluster status (red or yellow), unassigned shards, disks filling up node by node, and JVM heap pressure.

Типичное применение. Cluster status, unassigned shards, node disk and heap

Примеры

  • Elasticsearch 7, 8, 9
  • OpenSearch 1, 2, 3
  • The index behind Graylog or Wazuh

Как подключается

Что понадобится

  • Username / passwordA user holding only the cluster privilege monitor, sent as HTTP basic authentication.
  • Bearer tokenA service account token, sent as a bearer token. Elasticsearch API keys use another scheme and are not supported.

Учётная запись не нужна.

Сетевые порты, которые нужно открыть

  • 9200/TCPREST API (HTTP or HTTPS, default)
Шаги настройки: Create a monitoring-only Elasticsearch user
  1. Create a role that only holds the cluster privilege monitor, from Kibana (Stack Management, Roles) or with the API.

    curl -u elastic -X PUT "https://es.lan:9200/_security/role/dumbmonit" -H "Content-Type: application/json" -d '{"cluster":["monitor"]}'
  2. Create the user with that role.

    curl -u elastic -X PUT "https://es.lan:9200/_security/user/dumbmonit" -H "Content-Type: application/json" -d '{"password":"choose-a-long-password","roles":["dumbmonit"]}'
  3. OpenSearch: create a role with the cluster permission cluster_monitor in Security, Roles, and map the user to it.

  4. In DumbMonit, enter the address of one node, for example es.lan, then the user and its password.

  5. Elasticsearch 8 and later serve HTTPS with a generated certificate: pick HTTPS, and tick Accept an unverifiable certificate unless you installed your own.

Обратите внимание. The account needs no index privilege: DumbMonit never reads a document. One node reports the whole cluster, so enter a node that is not the one you expect to fail.

Ещё в категории «Базы данных и очереди сообщений»