Garmingo Docs

List

Browse and manage configured notification and automation integrations.

See every notification channel configured for your Status instance and confirm coverage.

What You Can Do Here

ActionPurpose
View ChannelsQuick audit of type, scope, active state
Toggle ActiveTemporarily pause noisy integrations
EditUpdate credentials or scope
DeleteRemove unused / compromised tokens

Columns (Typical)

ColumnMeaning
NameFriendly label you set (e.g. “Slack #prod”)
TypeChannel kind (Slack, Email, Webhook, etc.)
ScopeAll monitors or count of specific monitors
ActiveYes/No (delivery enabled)
CreatedWhen it was added

Filters

Filtering helps you locate and manage integrations efficiently in larger environments.

Available Filters

FilterWhat It DoesNotes
SearchFinds integrations by name or description keywordsUse specific terms for better results
EnabledShows only active or only disabled integrationsGreat for cleanup passes
MonitorsShows integrations linked to chosen monitors (or those set to “all monitors”)Helpful to see coverage gaps
TypesNarrows the list to certain channel types (e.g. Slack)Combine with Search for precision
From a MonitorListing opened from a monitor detail filters automaticallyQuick context pivot

How Search Works

Search results are automatically sorted by relevance before they are split into pages.

Usage Patterns

  • Show orphaned integrations: filter Enabled = enabled and Monitors empty (future UI feature; currently use metrics page).
  • Audit channel coverage: filter Type = critical channels (e.g., twilio-sms, opsgenie).
  • Reduce noise during migrations: disable a subset via Type + bulk action (planned feature).

Filters

Coverage Checklist

Use this list page together with metrics:

  • No critical monitor should show “no integration”.
  • At least one high‑urgency channel (SMS / Pager / Ops) for production monitors.
  • Avoid too many “All monitors” entries (can cause noise).

Housekeeping Tips

  • Quarterly review: remove stale or disabled entries.
  • Rename ambiguous labels (e.g. change “Webhook” -> “Webhook Incident Bridge”).
  • Rotate credentials on schedule (esp. Webhooks with long‑lived secrets).