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, select Channel and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Select Kener, then 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 Kener 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
Configure Kener
You need Kener 4.x and an account that can manage triggers and alert configurations in the admin console. The Kener server must be able to reach the Flashduty push URL.1
Create a webhook trigger in Kener
Where: Kener admin console › TriggersSave the trigger after filling in the fields.Kener renders the template without JSON escaping. The built-in default template includes
alert_message (the Details text of the alert configuration) and the site name. A double quote or a line break in either one makes the body invalid JSON, and Flashduty rejects the request, so both the alert and its recovery are lost. Use the template above, which leaves those fields out.2
Create an alert configuration in Kener and attach the trigger
Where: Kener admin console › Alerts
Save the configuration.
3
Verify
Where: Kener admin console › Triggers
- Use the trigger’s test button and confirm that Kener reports the request as sent. The test only proves that Kener can reach Flashduty, not that a real monitor is connected. The test request is a fixed body built into Kener (alert ID
1, severityWARNING, status randomlyTRIGGEREDorRESOLVED), and Flashduty handles it like any other alert:TRIGGEREDcreates or updates a Warning alert with Alert Key1, andRESOLVEDrecovers that alert, or creates nothing when no such alert is open. If the alert is still open after verifying, close it manually in Flashduty - Make a monitored service actually fail and confirm that an active alert appears in Flashduty once the failure threshold is reached, and the integration shows Latest event time
- Restore the service and confirm that the alert recovers once the success threshold is reached
Alert key
Flashduty uses the Keneralert_id as the Alert Key. Kener creates an alert record when a monitor reaches the failure threshold and updates the same record when it recovers, so the trigger and the recovery carry the same alert_id. If the same monitor goes down again, Kener creates a new alert_id, which is a new alert in Flashduty.
Changes to the monitor name, severity, status, or value do not change the Alert Key. A request without alert_id is rejected. alert_id is unique only within one Kener instance, so connect only one Kener instance to each Flashduty integration.
Status and severity
The alert title combines the monitor identifier, the alert type, and the value, for example
my-api STATUS: DOWN.
Labels
Troubleshooting
- Flashduty returns an invalid-parameter error: Confirm the URL is complete and includes
integration_key, and that the trigger uses the template on this page. The response names the missing field - The Kener trigger test fails: The test result shows the HTTP status code or network error. Confirm the Kener server can reach the Flashduty push URL
- An alert does not recover: Confirm the Success Threshold of the alert configuration has been met and the trigger is not disabled. Kener sends no recovery before the success threshold is reached
- No alert arrives: Confirm the alert configuration is active and has this trigger attached