Gestion des incidents
Connectez WizStatus à Zammad
Automatically open and close Zammad tickets when WizStatus detects incidents. The integration uses Zammad's HTTP Token authentication, supports priority and group routing, and adds articles for every incident state change to keep an auditable conversation in your helpdesk.
Avantages
- Automatic ticket creation when incidents fire
- Bi-directional sync: closing the Zammad ticket auto-resolves the WizStatus incident
- Priority derived from incident severity, overridable per channel
- Self-hosted helpdesk friendly (no SaaS lock-in)
- Full audit trail via ticket articles for every event
Guide de configuration
Suivez ces étapes pour configurer l'intégration
Generate a Zammad HTTP Token
In Zammad, open Profile > Token Access > "Add new". Grant ticket.agent permission and copy the generated token.
Attention
The token is shown only once — store it securely.
Identify the target group and customer
Decide which Zammad group should own the tickets (e.g. "Support") and the customer email used as the requester for monitoring tickets.
Astuce
Create a dedicated Zammad customer like monitoring@yourcompany to keep monitoring tickets isolated.
Configure the channel in WizStatus
Go to Settings > Alert Contacts, add a new channel, pick Zammad, and paste your instance URL, token, group and customer email.
Astuce
Override the priority if you want all alerts to land at the same Zammad priority instead of mapping from severity.
Send a test notification
Use the Test button on the channel card. WizStatus calls /api/v1/users/me to verify the token and reports the result.
Astuce
If the test fails, check that the token has ticket.agent rights and that the WizStatus pod can reach your Zammad URL.
Enable bi-directional sync (optional)
Generate a webhook secret in the channel form (or paste your own), then in Zammad Admin > System > Webhooks create a webhook pointing to https://wizstatus.com/api/monitoring/webhook/zammad/<channel_id>/, sign with the same secret (HMAC SHA256, header X-Hub-Signature-256), and attach it to a Trigger that fires on ticket state changes.
Astuce
Without the webhook the integration remains one-way: WizStatus opens and closes tickets, but closing a ticket in Zammad does not affect the WizStatus incident.
Options de configuration
Paramètres de configuration disponibles
| Option | Description | Requis |
|---|---|---|
Instance URL | Base URL of your Zammad instance (HTTPS recommended) | |
HTTP Token | Zammad HTTP token with ticket.agent permission | |
Group | Zammad group owning the created tickets | |
Customer Email | Email of the Zammad customer attached to the ticket | |
Priority | Override the severity-derived priority (1 low / 2 normal / 3 high) | |
Close State | Zammad state used on resolution (defaults to "closed") | |
Inbound Webhook Secret | Shared secret for HMAC SHA256 verification of inbound Zammad triggers. Required to enable bi-directional sync. |
Fonctionnalités
Restrictions
- Custom Zammad fields are not exposed in the channel config
Questions fréquentes
Prêt à commencer ?
Commencez à surveiller vos services en quelques minutes
Commencer gratuitementAucune carte de crédit requise • 20 monitors gratuits pour toujours