Integrations
Ozone delivers notifications and tickets from the on-prem Ozone Data Collector, not from the cloud. Each appliance runs a small outbound connector engine, and you configure connectors in the collector's WebUI Integrations page. When a problem or alert fires locally, the collector formats the event for each destination and posts it directly over HTTPS.
Delivering from the edge has one big benefit: notifications and tickets keep working during a WAN outage, because the appliance never needs the cloud to reach Slack, PagerDuty, or your ITSM.
Integrations are available on the Professional and Enterprise plans. See Licensing & Tiers.
How connectors work
Every connector follows the same pattern:
- Open Integrations in the collector WebUI and add a connector.
- Give it a destination (a webhook URL, a routing key, or an instance URL) and any credentials the destination needs. Credentials are stored as connector headers and are masked in the WebUI listing.
- Choose which events route to it. A connector fires when its event list contains the event type, or when it is set to all events.
- Use Test to send a sample event and confirm the destination receives it before you route real traffic.
Delivery is best effort: each connector is posted independently with a short timeout, so a slow third-party API never blocks the collector's local pipeline. Destinations are validated before every send (loopback, link-local, cloud-metadata, and reserved addresses are refused), while private on-prem addresses are allowed so you can point ServiceNow, Jira, or a webhook at an internal system.
Connector catalogue
| Connector | What it does | You provide |
|---|---|---|
| Slack | Posts a message to a Slack channel through an incoming webhook | Channel webhook URL |
| Microsoft Teams | Posts a message to a Teams channel through an incoming webhook | Channel webhook URL |
| Webex | Posts a message to a Webex space | Space incoming-webhook URL |
| PagerDuty | Triggers an incident through the Events API v2, mapped to Ozone severity | Service routing key |
| ServiceNow | Creates an incident record (short description, description, urgency, impact) | Instance URL and credentials |
| Jira | Creates an issue in a project (summary, description, issue type) | Base URL, project key, credentials |
| Generic webhook | Posts a JSON event to any HTTPS endpoint you control | Endpoint URL, optional custom headers |
The generic webhook payload is a small JSON object with the event type, a human-readable summary, the event data, and a timestamp. Add your own authentication headers if the receiver needs them.
The PagerDuty connector maps Ozone problem severity to PagerDuty severity (P1 to critical, P2 to warning, everything else to info), so your existing on-call schedules and escalation policies apply automatically.
Edge config-change correlation (Netshot)
The Ozone Data Collector can also integrate with Netshot so a configuration change captured on your network gear lines up in time with the events Ozone reports. This turns "what changed right before this incident" into a direct, on-box correlation. It is configured on the collector alongside the connectors above.
When a connector stops delivering
Check the connector's delivery status in the collector WebUI Integrations page first, then re-run Test. If Test fails, the collector reports the destination's HTTP status or the reason it was blocked. For deeper edge faults, see Collector Troubleshooting.