Skip to main content
Resolve investigates the alerts you send it, and every source arrives one of three ways: a webhook, an AWS polling source, or a chat channel. This page finds your path and sends you to the one page that sets it up.

​
How an alert reaches Resolve

  1. Your source delivers the alert: a webhook call, a polled AWS service, or a message in a chat channel Resolve watches.
  2. Pulse drops duplicates and noise. What survives is a signal.
  3. Pulse groups related signals into a cluster: one problem, however many alerts it produced.
  4. A cluster that holds an actionable signal is filed as an incident — matched to an open one, or opened as a new one. While On duty, CloudThinker investigates it on its own.
Whichever path you take, you set it up in one place: Resolve → Integrations. Every path needs the workspace Admin role and admin access to the tool that produces the alerts. See Roles.
Resolve Integrations page with platforms grouped by readiness and a search field

Resolve Integrations: platforms grouped by readiness, Needs attention first

Delivery and investigation are separate settings. While On duty shows Paused, your sources keep delivering and an actionable cluster is still filed as an incident with status Open: what waits is automatic triage and investigation, until someone clicks Investigate. See What starts an investigation.

​
Choose your path

A successful response from a webhook only proves delivery. Confirm one signal on Resolve → Pulse before you rely on any source.

​
Tools with a preset

A preset is the field mapping and severity mapping Resolve fills in when you pick a tool, so you don’t have to work out which part of the payload holds the title or the severity. These tools have one: A preset also picks the authentication the tool supports: PagerDuty signs its webhooks, and CloudWatch sends a named key header. A filled-in mapping isn’t a verified one. Check it against a real payload before you trust it, because a preset can point at a field your tool doesn’t send: the Datadog preset’s service path is one example. See Map the fields. Anything not in this table goes through a custom source, where you map the fields by clicking them in a payload your system really sent.

​
Next steps

Set up a webhook signal

Map a listed tool’s alerts into Pulse and choose when CloudThinker investigates.

Connect Pulse sources

Add a webhook, an AWS polling source, or a chat channel, then confirm it delivers.

Add a custom signal source

Connect a system with no preset by clicking the fields in its own payload.

Check what's connected

Read each platform’s connection, signals, and readiness badge.