Mark device response as underway
Once someone starts working on a device-related incident, acknowledge it through your alerting webhook to signal active ownership and prevent further escalation.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Acknowledge Incident
Acknowledges an active incident, stopping further escalations.
Why this helps
An incident can keep escalating after a responder has started work if nobody marks it as being handled.
- Marks an ongoing incident as actively being addressed.
- Helps prevent additional escalation after work has begun.
- Uses an incident identifier supplied by your alerting setup.
Setup
Build it in a few focused steps.
- 1Connect Better Stack in Notis and configure an external sender to post a Better Stack incident ID to a Notis webhook when response work begins.
- 2Create an automation in Notis and name it for device incident acknowledgment.
- 3Tell Notis to acknowledge the ongoing Better Stack incident identified in the webhook request.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real ongoing incident and confirm its acknowledgment in Better Stack.
Questions about this workflow
Will the Adafruit IO alert automatically acknowledge an incident?
Only if your external sender posts the incident identifier to the Notis webhook at the point your team considers response to have started. Adafruit IO has no listed trigger event here.
What happens when the incident is acknowledged?
Better Stack marks the ongoing incident as being worked on, which prevents further escalations.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Better stack. A trigger fires from one place; an action lands in another.
Adafruit IO triggers
Better stack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Escalation Policy
Creates an incident escalation policy that defines who is notified and when.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Acknowledge Incident
Acknowledges an active incident, stopping further escalations.
Create Heartbeat Group
Creates a group to organize related heartbeat checks.
Create Outgoing Webhook Integration
Creates an integration to send event notifications to an endpoint.
Create Heartbeat
Creates a heartbeat monitor that checks for regular signals from a service.
Create Source Group
Creates a group to organize related log sources.
Delete Escalation Policy
Permanently deletes an escalation policy.
Create Incident
Creates an incident and alerts the on-call responder through the applicable escalation policy.
Connect any two apps with Notis in the middle.
Adafruit IO and Better stack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Better stack.