Use Cases
Custom actions are essentially Webhook calls. You can add custom actions for incidents in different channels and manually trigger them in incident details to achieve quick troubleshooting or information sync.Restart Host
When host memory or CPU is maxed out, trigger host restart script for quick restart
Information Enrichment
When incidents occur, callback your service to retrieve Tracing, Logging, topology info based on alert details, and actively call Flashduty Open API to update incident information
Rollback Changes
When incidents occur, if confirmed to be caused by changes, directly trigger callback to your deployment platform to start rollback process
Update Status Page
When confirmed that incidents affect production services, trigger external Status Page update to promptly notify your customers or partners
Configure Custom Actions
Configure Information
Configure the following:
| Field | Description |
|---|---|
| Action Name | This name appears as a button in incident details |
| Channels | Can configure multiple, but each channel allows at most three custom actions |
| Endpoint | HTTP(s) address triggered when clicking custom action button |
| Custom Headers | Custom headers included when requesting the Endpoint |