Documentation
- Getting Started Configuration
- OpenID & LDAP
- Custom TLS Certificate
- Custom OS Images
- Extra Files
- Network Interface Bonding
- Multipath disks
- Accessing your Cluster
- CephFS
- MDS Notifications
- CephFS Guard
- RBD
- S3
- S3 Multisite
- NVMe over Fabrics
- SMB
- NFS
- Ceph Keys
- Updating croit
- Replacing OSDs
- Replacing NIC
- PG numbers
- Updating Ceph
- Migrating or restoring croit container
- Backups
Sur cette page :
Monitoring & Alerting
You can use hook scripts to setup and configure monitoring on your croit installation.
Hook Script Library
croit ships with a hook script library with the following options:
Monitoring
- CheckMK
- SNMP
- Zabbix
The monitoring scripts install their agent on every server each time it boots. Before you add one, check what it needs:
- CheckMK downloads the agent from your CheckMK site and registers the server with it. Create each server as a host in the site first, under the same name croit shows for it, and enter the site's hostname or IPv4 address without a port: the script reaches the site over HTTP on port 80. CheckMK's agent controller does not accept an IPv6 address, so a site reached over IPv6 needs a hostname.
- SNMP installs
net-snmpfrom the AlmaLinux package repositories, so your servers need to reach them. If the install fails, the script stops there and reports a non-zero exit instead of configuringsnmpd. - Zabbix downloads the agent from
repo.zabbix.com, so your servers need to reach it.
To try a script before your servers reboot, select it under Config → Hook Scripts and click Execute. The task log shows the script's output and its exit code.
Alerting
- Discord
- Slack
- Telegram
Do you need help integrating croit into your environment? Did you already write your own script and want to contribute it to our hook script library?
Don't hesitate to contact us!
