Alarms to SNMP, syslog, Zabbix and your NOC
Checks decide when something is wrong; incidents record it with a severity; alarm export sends it to the people and systems that do not watch the probe. Every target has a filter and a test button.
- SNMP v2c/v3
- Syslog TLS
- Zabbix
- Nagios
- Webhooks
- Slack
- Teams
- REST API

Four severities, one meaning everywhere
Every incident is CRITICAL MAJOR MINOR or INFO, on every page, in the summaries and in every alarm target.
- Logged once at the start and once at the end, with duration and count
- History over days, per flow and on the Incidents page
- No Data stays open until the flow sends again, then says how long it was silent
- Picture evidence and loudness graphs kept with the incident
Checks with profiles and overrides
Settings > Checks has a card per category. Each check has on or off, a severity and its values in units.
- Overrides for all flows, a group, a flow, an MPTS program or a PID; the most specific wins
- A trigger raises an alarm only after N occurrences in a time window
- Bitrate low and high, timing, loudness, picture, ETR 290 and ST 2022-7 checks
- Each check type explained, with a link to its manual section

Alarm export targets
Nothing is sent until a target is switched on. Alarms carry the probe name, the flow and, for MPTS, the service name and program number. A Test connection button checks a target with the values as typed, and names the step that failed.
| Target | Transport | Notes |
|---|---|---|
| Alert Center | WebSocket (wss) | DVBControl Alert Center, acknowledge from a severity |
| Syslog | UDP, TCP, TLS | Up to 4 receivers, structured data, heartbeat |
| SNMP traps | SNMPv2c, SNMPv3 | IP-Probe MIB, SHA-256 / AES-128 for v3 |
| SMTP, STARTTLS, TLS | Up to 20 recipients, daily or weekly digest | |
| Zabbix | Sender or polling | Zabbix template to download |
| Nagios, Icinga, Checkmk | Polling | check_ipprobe plugin, read-only API key |
| Slack, Microsoft Teams | Webhook | Formatted per target |
| Webhooks | HTTPS JSON | Batching, HMAC-SHA256 signature |
Built for a NOC
- Heartbeat with the number of active alarms, so a silent probe differs from a quiet one
- Send repeats per target for a continuing error
- Severity per alarm type for all targets
- Secrets are write-only and not in a backup

Control from outside
Start and download recordings, read the alarm status, change the configuration. Every change is in the audit log with user and source.
Read-only keys
For Zabbix and Nagios polling. The key is shown once; the probe keeps only a fingerprint. Optional expiry date.
Roles and passkeys
Admin, NOC and Management roles, passkey login with the password as fallback, HTTPS with your certificate.
Which options this needs
Incidents, checks, alarm export and the REST API are part of the Base option on every probe. How licensing works.