Integrations & API
otwatch alerts reach people and tools through Alertmanager. All components offer documented HTTP APIs for automation.
Notification channels
| Channel | Use |
|---|---|
| Jira Service Management | Tickets with priority and SLA timers, on-call schedules, escalation, acknowledgement; bidirectional |
| Microsoft Teams | Notifications to a team channel |
| Notifications and reports | |
| SMS, phone call, mobile push | On-call for critical alerts via Jira Service Management |
| Webhook / REST | Any system with an HTTP interface, e.g. ServiceNow, Splunk or an in-house tool |
ITSM: Jira Service Management and ServiceNow
- Alerts create and update tickets automatically, including priority, affected component, environment and links to dashboard and runbook.
- Repeated alerts update the existing ticket instead of creating duplicates; tickets are resolved when the alert clears.
- ServiceNow is connected via Event Management or the Incident API, either directly by webhook or through Jira Service Management.
APIs
| Component | Typical automation | Documentation |
|---|---|---|
| Prometheus | Query metrics, targets, rules and alerts | HTTP API |
| Alertmanager | Create maintenance windows (silences) from change management, read alerts | API v2 |
| Grafana | Dashboards, folders, users, annotations, data queries | HTTP API |
| Loki | Query logs | HTTP API |
API access uses service account tokens with role-based permissions. Prometheus, Alertmanager and Loki APIs are only reachable through the authenticated access path agreed with the customer.
Further reading
handel gmbh · otwatch documentation · Last updated 19 October 2026