1. Home
  2. Features
  3. Alarms and integration
Feature area 04 / 06

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
  • Email
  • Webhooks
  • Slack
  • Teams
  • REST API
Incidents page of IP-Probe with the number of episodes per hour and a list of incidents with severity
FIG 01Incidents page: episodes per hour and the incident list
INCIDENTS

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

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
Settings Checks page with check instances, their types and parameters
FIG 02Settings > Checks: instances, types and parameters

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.

TargetTransportNotes
Alert CenterWebSocket (wss)DVBControl Alert Center, acknowledge from a severity
SyslogUDP, TCP, TLSUp to 4 receivers, structured data, heartbeat
SNMP trapsSNMPv2c, SNMPv3IP-Probe MIB, SHA-256 / AES-128 for v3
EmailSMTP, STARTTLS, TLSUp to 20 recipients, daily or weekly digest
ZabbixSender or pollingZabbix template to download
Nagios, Icinga, CheckmkPollingcheck_ipprobe plugin, read-only API key
Slack, Microsoft TeamsWebhookFormatted per target
WebhooksHTTPS JSONBatching, 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
Alarm export settings with the Alert Center target and the list of targets
FIG 03Settings > Alarm export: one tab per target
REST API

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.

API keys

Read-only keys

For Zabbix and Nagios polling. The key is shown once; the probe keeps only a fingerprint. Optional expiry date.

Users

Roles and passkeys

Admin, NOC and Management roles, passkey login with the password as fallback, HTTPS with your certificate.

LICENSE: Base

Which options this needs

Incidents, checks, alarm export and the REST API are part of the Base option on every probe. How licensing works.

Contact

Tell us what runs on your network.

Send the standards, the port speeds and the number of flows you need to watch. An engineer answers, not a call center. License and evaluation requests go the same way.

RTSS B.V.
Oude Enghweg 1
1217 JA Hilversum
The Netherlands

Phone +31 35 7 130 150