Skip to main content
Pulse pulls signals from three source families — AWS service pollers, chat platforms (Slack and Teams), and third-party monitoring webhooks — all configured from the Manage subscriptions page. Once a source is wired, Pulse deduplicates and classifies every event, and clusters that cross the actionability bar escalate to an incident where agents investigate root cause.

​
Prerequisites

  • A CloudThinker workspace — new to Pulse? Read How it works first
  • An active AWS connection with read permissions for the services you want to poll
  • The CloudThinker bot installed in Slack or Teams, if you want chat-channel signals
  • A monitoring tool that supports outbound webhooks, if you want third-party signals

​
Wire monitoring into incidents

This is the end-to-end flow: connect a source, confirm signals arrive, and let actionable clusters escalate to incidents.
1

Open Pulse

Go to Pulse in your workspace and click Manage subscriptions. The page lists all three source families and their current status.
2

Add at least one source

Enable an AWS poller, subscribe a chat channel, or point a monitoring webhook at CloudThinker — the three procedures below cover each path.
3

Confirm signals arrive

Send a test alert from your monitoring tool, or wait for the next polling cycle.Success state: new signals appear in the Pulse feed with a category, severity, and one-line summary.
4

Escalate a cluster to an incident

Pulse auto-escalates clusters with Critical or High severity signals, or any signal the AI marks actionable. For anything else, click Escalate on the cluster.Success state: a linked incident is created and root cause analysis begins with the cluster’s full signal history as starting context.

​
AWS polling

AWS polling lets Pulse pull events directly from your AWS accounts on a schedule — no webhook configuration required. Each source is enabled per connection.

​
Enable a poller

1

Open polling settings

In Pulse, click Manage subscriptions and go to the AWS Polling section. You see your connected AWS accounts and their current polling status.
2

Validate first

Click Validate next to the source. Pulse performs a dry run to confirm your credentials have the required read permissions.Success state: a clear ✓ means ready; an error code (e.g. AccessDenied) tells you exactly what’s missing.
3

Enable

Toggle the source on. Pulse starts polling immediately.
If a poller fails five consecutive times, Pulse pauses it automatically and surfaces the error code. To resume: fix the issue, re-validate, then re-enable the toggle.

​
Slack and Teams subscriptions

When the CloudThinker bot is present in a channel, messages in that channel become Pulse signals — alert bot posts, incident announcements, on-call chatter — classified alongside your infrastructure events.
Create Subscription dialog with Platform dropdown set to Slack, Channel search field, invite instruction callout, and Enabled toggle

Select a platform, pick a channel, invite the bot, save

1

Select platform

Choose Slack or Microsoft Teams.
2

Pick a channel

Search for the channel you want to monitor.
3

Invite the bot (Slack only)

Run /invite @CloudThinker in the target channel — Slack only delivers messages to apps that are channel members.
4

Save

Enabled is on by default. Click Create subscription.
Subscriptions can be toggled on and off independently — useful for muting a channel during a maintenance window without losing the configuration.

​
Channel types

​
Third-party webhooks

Any monitoring tool that supports outbound webhooks can send signals to Pulse — Datadog, Grafana, PagerDuty, and more ship with built-in field mapping.
1

Create a webhook endpoint

Go to Webhooks in CloudThinker and create an endpoint — see Webhooks for full setup.
2

Point your monitoring tool at it

Paste the generated URL into your tool’s webhook or notification settings. Platform-specific instructions, authentication options, and field mappings live in Webhook integrations.
3

Send a test alert

Use your monitoring tool’s test feature.Success state: the alert appears as a signal in the Pulse feed within moments.

​
Signal categories

Every signal — regardless of source — is assigned one of eight categories:

​
Next steps

Clusters

Triage the cluster lifecycle — from Active to Routed to Resolved

Webhook integrations

Platform-specific setup for Datadog, Grafana, PagerDuty, and more

Root cause analysis

See how agents investigate escalated incidents to a confident root cause

Pulse analytics

Measure noise reduction and signal trends across your sources