Quick test
Works with any source type to validate credentials and connectivity:Connectivity test
HTTP/1.1 202 Accepted.
With
info severity, aciona.me creates the incident but does not send push — that is normal behavior for informational alerts. Use critical if you want to validate the notification on your phone.Full test
1
Trigger from the tool itself
Use its native test feature (test notification, test workflow, force alarm state) or force the alert condition. That validates the real payload, not one you made up.
2
Confirm the incident
Under Incidents, check title, severity, service and owner. If the service is wrong, adjust the service hint the tool sends.
3
Confirm the notification
You should receive it through the configured channels. If not, see Notification not received.
4
Acknowledge the incident
Validate that ACK works through the channel your team actually uses — push, email or the Slack card.
5
Test the recovery
Bring the condition back to normal (or force the recovery) and confirm the incident was resolved automatically. This is the most-skipped step — and the one that fails most often in production.
Validation checklist
-
202 Acceptedon ingestion - Incident created with the correct service
- Severity translated as expected
- Owner resolved by the schedule
- Notification received on the right channel
- ACK working through the team’s channel
- Second trigger aggregated, not duplicated
- Recovery resolving the incident automatically