Skip to main content
Use DBmarlin’s Webhook integration to send database instance and host alerts to Flashduty On-call. The “started” and “ended” notifications of one alert rule on the same instance or host update one Flashduty alert, which recovers when the alert ends. DBmarlin’s webhook has no fixed format: you write the request body in the Content Template. The templates on this page are the format Flashduty parses, so copy them as is.

In Flashduty On-call

Create either a dedicated or shared DBmarlin alert integration and copy its complete Push URL.

Configure DBmarlin

The Webhook integration requires DBmarlin v5.11 or later, and the webhook you create is marked Default and enabled, which is what sends alerts.
1

Create a Webhook in DBmarlin and enter the URL

Where: DBmarlin › Settings › Integrations › Webhook › Edit › Webhooks page › Create
2

Enter the Content Template and Host Content Template

Where: DBmarlin › Settings › Integrations › Webhook › Edit › Create › Content Template / Host Content TemplateInstance alert template:
Host alert template:
Keep ruleid, startedended, and either instance (instance alerts) or node (host alerts). Flashduty rejects a request without the rule ID or the instance/host name, because it could not reliably match the later “ended” notification. The template must be valid JSON.
3

Enable the Webhook and create an alert rule

Where: DBmarlin › Settings › Integrations › Webhook › Edit, then DBmarlin › Settings › Alert RulesSave and enable the integration (a Webhook you create is marked Default and enabled). Under Settings → Alert Rules, create a rule that is easy to trigger.
4

Verify with a real alert

The DBmarlin docs do not mention a test button for the Webhook, so verify with a real alert: wait for DBmarlin to send the “started” notification and confirm Flashduty shows an active alert. When the rule clears, DBmarlin sends the “ended” notification; confirm the same alert recovers. A few seconds later the integration in Flashduty shows a Latest event time, which means setup works.

Alert key

Flashduty computes the Alert Key from the rule ID (ruleid) plus the instance name (instance) or host name (node); instance alerts and host alerts never share a key. The “started” and “ended” notifications of one rule on the same instance or host share one Alert Key; changes to from, to, values, and the rule name do not change it.
  • If you delete a rule and recreate it, it gets a new rule ID and the old alert is not resolved; close it manually
  • When the same rule fires again, it uses the same Alert Key

Status and severity

The webhook body carries no severity, so every alert is treated as Warning. DBmarlin sends startedended in upper case (STARTED, ENDED); Flashduty ignores the case, treats a value starting with end, or equal to resolved, cleared or ok, as the end, and any other value as a start.

Recovery and auto-close

DBmarlin sends an “ended” notification when an alert ends, and Flashduty uses it to recover the alert. To keep a lost notification from leaving an alert open, configure auto-close after timeout on the channel or integration, longer than your rules can stay active.

Troubleshooting

  • DBmarlin logs status code 400: confirm the template is valid JSON and contains ruleid, plus instance (instance alerts) or node (host alerts)
  • 404 or 401: confirm the Webhook URL is complete and contains integration_key
  • The alert does not recover: confirm DBmarlin sent the “ended” notification and the template contains startedended; a double quote or backslash in a rule name breaks the JSON, so avoid them
  • Host alerts do not arrive: host alerts use the Host Content Template, not the Content Template
For more details, see the DBmarlin Webhook documentation.