DumbMonit
IntégrationsMétriques et journaux
Surveiller Graylog avec DumbMonit
The log server and its search cluster: processing, journal backlog, buffers, throughput in and out, OpenSearch health, failed inputs and indexing failures.
DocumentationSite officiel : Graylog
Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.
Ce que DumbMonit surveille
The log server and the search cluster behind it: whether Graylog processes messages, how many wait in its journal, how full its buffers are, what comes in and what goes out, the health of OpenSearch or Elasticsearch as Graylog sees it, inputs that failed to start, and messages that failed to be indexed.
Usage typique. Log server and its OpenSearch cluster: journal, buffers, throughput, inputs
Exemples
- Graylog Open
- Graylog with OpenSearch
Comment il se connecte
Ce qu'il faut
- Access token (recommended)A token of the dedicated Graylog user, created from its Edit tokens page.
- User name / passwordThe dedicated Graylog user itself, sent as HTTP basic authentication.
Ports réseau à ouvrir
9000/TCPGraylog REST API (default)
Étapes de mise en place: Create a read-only user and token in Graylog
Open System → Users and Teams → Create user, name it as follows, give it a long random password and assign the Reader role only.
dumbmonitOpen that user's Edit tokens page, create a token named after DumbMonit and copy it: Graylog shows it only once.
Optional, for Graylog's own notifications: with an account that can manage roles, create a role holding only notifications:read and give it to the dumbmonit user.
curl -u YOUR_USER -H 'X-Requested-By: cli' -H 'Content-Type: application/json' -X POST https://graylog.lan/api/roles -d '{"name":"DumbMonit Notifications","description":"Read system notifications","permissions":["notifications:read"],"read_only":false}' curl -u YOUR_USER -H 'X-Requested-By: cli' -X PUT 'https://graylog.lan/api/roles/DumbMonit%20Notifications/members/dumbmonit'In DumbMonit, enter the Graylog node address (for example graylog.lan, port 9000) and paste the token. In a cluster, add each node.
À savoir. Do not reuse your own account: a leaked token carries every right of its user. Graylog serves plain HTTP unless TLS is configured: across an untrusted network, put it behind HTTPS.