Introduction
Overview of integration channels linking monitors, incidents, and maintenance to external tools.
Integration Types
Current built‑in types (see individual pages for setup):
- Discord Webhook
- Slack
- Microsoft Teams
- Twilio SMS / Call
- Webhook (generic POST)
- Mobile App (push)
- Jira, Trello, OpsGenie
- Telegram, Mattermost, Rocket.Chat, Signal
Each type may require validation (e.g., email verification link) before activation.
Scope & Targeting
An integration can be configured to:
| Mode | Behavior |
|---|---|
| All Monitors | Receives events from every monitor automatically (future monitors included). |
| Selected Monitors | Only triggers for the chosen subset (modifiable later). |
Activation State
active: true=> notifications dispatchedactive: false=> retained configuration, no messages
Deduplication Strategy
Garmingo groups status changes (flapping reduction) using retry logic at the monitor layer; integrations receive only committed state transitions after retries (except heartbeat/manual which have no retries).
Metrics (Why Some Numbers Matter)
| Metric | Purpose |
|---|---|
| Monitors without integration | Highlights blind spots (no notification path). |
| Integrations without monitors | Cleanup candidates (unless set to All). |
| Used integrations | Adoption / cost tracking. |
Security & Reliability
- Secrets (tokens, webhook URLs) are stored server‑side and never re‑exposed in full after creation.
- Email integrations enforce address verification via signed link.
Best Practices
- Use at least two channels for critical infrastructure (e.g., Slack + SMS).
- Keep "All monitors" integrations minimal—prefer targeted sets to reduce noise.
- Periodically audit inactive integrations to remove stale credentials.
