Update Gitea wiki: fix Zabbix host name to AgapHost

2026-02-21 17:25:18 +00:00
parent 3dddf55e5e
commit 7d1fb779f4

@@ -52,21 +52,23 @@ Config: `/etc/zabbix/zabbix_agent2.d/gitea_backup.conf`
### Creating Zabbix Trigger Alerts
1. **Create items** — go to *Data collection → Hosts → agap → Items → Create item*:
1. **Create items** — go to *Data collection → Hosts → AgapHost → Items → Create item*:
- Name: `Gitea backup status`, Key: `gitea.backup.status`, Type: Zabbix agent (active), Type of information: Numeric (unsigned), Update interval: `1h`
- Name: `Gitea backup age`, Key: `gitea.backup.age`, Type: Zabbix agent (active), Type of information: Numeric (unsigned), Update interval: `1h`
2. **Create triggers** — go to *Data collection → Hosts → agap → Triggers → Create trigger*:
2. **Create triggers** — go to *Data collection → Hosts → AgapHost → Triggers → Create trigger*:
- **Backup failed:**
- Name: `Gitea backup failed`
- Severity: High
- Expression: `last(/agap/gitea.backup.status)=0`
- Expression: `last(/AgapHost/gitea.backup.status)=0`
- **Backup stale (>25h):**
- Name: `Gitea backup is stale`
- Severity: Warning
- Expression: `last(/agap/gitea.backup.age)>90000 or last(/agap/gitea.backup.age)=-1`
- Expression: `last(/AgapHost/gitea.backup.age)>90000 or last(/AgapHost/gitea.backup.age)=-1`
3. **Verify** — go to *Monitoring → Latest data*, filter by host `agap` and key `gitea.backup`, confirm both items return values.
3. **Verify** — go to *Monitoring → Latest data*, filter by host `AgapHost` and key `gitea.backup`, confirm both items return values.
> **Note:** Items and triggers are already configured via the Zabbix API.
## Stack