Administration / Monitoring and status
Monitoring with Zabbix
Checked against Zabbix documentation, November 2026.
Zabbix reads the metrics of Lunedo with an HTTP agent item and splits them with Prometheus preprocessing; no template is needed. monitoring.md lists every metric and explains the token.
-
Create a host for the instance and a macro
{$LUNEDO.METRICS.TOKEN}of the type secret text with the metrics token. -
Add a master item of the type HTTP agent: URL
http://lunedo:3000/metrics, request type GET, headerAuthorizationwith the valueBearer {$LUNEDO.METRICS.TOKEN}, type of information Text, update interval1m, history Do not store (only the dependent items keep values). -
Add a dependent item per value with Prometheus pattern as its first preprocessing step and value as result processing, for example:
Item Key (your choice) Pattern Type Storage used storage.usedlunedo_storage_usage_ratioNumeric (float); add the preprocessing step Custom multiplier 100for percentStorage level storage.levellunedo_storage_levelNumeric (unsigned) Last backup backup.lastlunedo_backup_last_success_timestamp_secondsNumeric (unsigned), unit unixtimeFailed mails mail.undeliveredlunedo_mail_undelivered_totalNumeric (unsigned), then the preprocessing step Change per second or Simple change Maintenance mode maintenancelunedo_maintenance_modeNumeric (unsigned) Collaboration server collab.uplunedo_collab_upNumeric (unsigned) Version versionlunedo_build_info, result processing label with the labelversionCharacter -
For the job queues, add a discovery rule as a dependent item with the preprocessing Prometheus to JSON and the pattern
lunedo_jobs{state="failed"}, the LLD macro{#QUEUE}from$.labels['queue'], and an item prototype with the patternlunedo_jobs{queue="{#QUEUE}",state="failed"}. -
Add triggers with the thresholds of the Prometheus alerts, for example, for a host named
lunedo,now() - last(/lunedo/backup.last) > 26handlast(/lunedo/storage.level) >= 1.
Use the address inside the network, not the public address of the reverse proxy. The host itself (CPU, memory, disk of the volumes) is monitored by the Zabbix agent as usual.