In Flashduty On-call
You can get the integration push URL in either of the following ways.Use a dedicated integration
- In the Flashduty console, go to Channels and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Select Cronicle and click Save
- Open the generated integration card and copy the Push URL
Use a shared integration
- In the Flashduty console, go to Integration Center → Alert Events
- Select Cronicle and enter an integration name
- Configure the default route and select a channel. You can add more rules under Routing after creation
- Click Save and copy the generated Push URL
In Cronicle
1
Set the Web Hook URL in Cronicle
Pick one of the locations below and enter
{integration_url}:- Single event
- Category
- All events
Where: Cronicle › Schedule › Edit Event › Event Notification › Web Hook URLEdit the event in Schedule and paste the URL into Web Hook URL in the Notification area.
Cronicle sends an HTTP POST request (JSON) when a job starts and when it ends. Flashduty only processes job completion (
job_complete) and launch failure (job_launch_failure); job start (job_start) notifications are acknowledged and ignored. To stop sending start notifications, remove the job_start entry from web_hook_text_templates.2
Turn on auto-close timeout
Where: Flashduty console › ChannelsAn alert only closes when the next job of the same event completes successfully. Events that are deleted, disabled or no longer run never send a recovery, so edit the channel that receives these alerts and turn on auto-close timeout; we recommend 24 hours.
3
Trigger a failure and verify the lifecycle
Run the event with a job that fails (for example, a script that exits with a non-zero code). Confirm Flashduty receives a Critical alert and the integration shows Latest event time; then fix the script and run it again, and confirm the original alert closes automatically.
Payload
Cronicle POSTs the following fields as JSON. Flashduty parses them directly, with no template to configure:
The body also contains the event parameters (
params) and the web hook URL (web_hook). Flashduty neither reads nor stores these two fields.
Alert key
Flashduty usesevent (the event ID) as the Alert Key. Every job of the same event carries the same event, and only the job ID id changes per run, so failures, launch failures, and the later success of one event land on the same alert. Changing the event title, the exit code, or the server that ran the job does not change the Alert Key.
Status and severity
Cronicle notifications carry no severity, so a failed scheduled job is treated as Critical:
The Cronicle web hook has no test button. To check connectivity, run an event once.
FAQ
If a job has retries configured, do I get a notification for every failed attempt?
If a job has retries configured, do I get a notification for every failed attempt?
No. Cronicle sends
job_complete only when the job finally ends, after retries are used up. It sends nothing between retries.Are launch failures sent repeatedly?
Are launch failures sent repeatedly?
Yes. A scheduled event tries to launch again every minute, and while the target server is unavailable each attempt sends
job_launch_failure. These notifications carry the same Alert Key and merge into one alert, so they do not create multiple alerts.Can I send only some events?
Can I send only some events?
The Web Hook URL can be set on a single event or on a category, so fill it in only where you need it. You can also split traffic in the routing rules of a Flashduty shared integration, by label
event_id or check.Troubleshooting
- Cronicle does not send anything: confirm the Web Hook URL is the complete push URL including
integration_key, and setdebug_levelto 9 to seeWeb Hook ErrorandWeb Hook Responseentries in the Cronicle log - Flashduty returns a parameter error: confirm the body contains
actionandevent, and thatjob_completenotifications containcode - The alert does not recover: confirm a later job of the same event ended with
code0, and that the event has a Web Hook URL