DBmarlin Integration

Create alerts in ilert from DBmarlin alert rules — with ilert's DBmarlin inbound integration.

DBmarlin is a database observability and performance monitoring tool that tracks database instances, hosts, and the changes that affect them. Its alert rules watch statistics such as query time, executions, or host CPU and fire when a threshold is breached. With this integration, DBmarlin alert rules automatically create alerts in ilert, so the right responders are notified and escalations happen reliably.

In ilert: Create a DBmarlin alert source

1. Go to Alerting → Alert sources and click on Create new alert source

   
2. Search for DBmarlin in the search field, click on the tile and click on Next.

   
3. Give your alert source a name, optionally assign teams and click Next.
4. Select an escalation policy by creating a new one or assigning an existing one.

   
5. Select your Alert grouping preference and click Continue setup. You may click Do not group alerts for now and change it later.

   
6. The next page shows additional settings such as custom alert templates or notification priority. Click on Finish setup for now.
7. On the final page, ilert generates a webhook URL for your alert source in the form https://api.ilert.com/api/v1/events/dbmarlin/<api-key>. Copy it — you will need it in the next section. You can find it again later under the alert source's Settings tab.

In DBmarlin: Enable the Webhook integration

1. In the DBmarlin sidebar, go to Settings --> Integrations.

   
2. In the Alert notification section, find the Webhook row and click on Edit.

   
3. Click on Create to add a new webhook integration.

   

In DBmarlin: Create the ilert webhook

Fill in the Create Webhook Integration form:

• Name: a name for the webhook, for example ilert webhook
• Webhook URL: the webhook URL you copied from your ilert alert source
• DBmarlin URL: the base URL of your DBmarlin installation, for example http://localhost:9090. DBmarlin uses it to build the deep link that is sent to ilert as dbmarlinUrl, so responders can jump straight from the ilert alert into DBmarlin.
• Headers: click on Add Header and add Content-Type with the value application/json
• Content Template: the payload for database instance alert rules — copy and paste the template from Content template below
• Host Content Template: the payload for host alert rules — copy and paste the template from Host content template below

Then save the webhook and make sure both the webhook itself and the Webhook integration on the Integrations page are toggled to Enabled.

Finally, attach the webhook to your alert rules: mark it as Default so every alert rule uses it, or select it on individual rules under Settings --> Alert Rules.

Content template

Used for alert rules on database instances. The datasourceName field carries the name of the monitored instance.

{
  "body": {
    "datasourceName": "<datasourcename>",
    "hostname": "<hostname>",
    "severity": "3",
    "summary": "<rulename>: <statistic>",
    "ruleId": "<ruleid>",
    "ruleName": "<rulename>",
    "statistic": "<statistic>",
    "oldValue": "<oldvalue>",
    "newValue": "<newvalue>",
    "threshold": "<threshold>",
    "units": "<units>",
    "from": "<from>",
    "to": "<to>",
    "timezone": "<tz>",
    "dbmarlinUrl": "<url>",
    "interval": "<interval>"
  }
}

Host content template

Used for alert rules on hosts. Instead of datasourceName it carries eventType, which DBmarlin populates with the substitution variable <startedended> — that is, whether the alert condition started or ended.

{
  "body": {
    "eventType": "<startedended>",
    "hostname": "<hostname>",
    "severity": "3",
    "summary": "<rulename>: <statistic>",
    "ruleId": "<ruleid>",
    "ruleName": "<rulename>",
    "statistic": "<statistic>",
    "oldValue": "<oldvalue>",
    "newValue": "<newvalue>",
    "threshold": "<threshold>",
    "units": "<units>",
    "from": "<from>",
    "to": "<to>",
    "timezone": "<tz>",
    "dbmarlinUrl": "<url>",
    "interval": "<interval>"
  }
}

Both templates use DBmarlin substitution variables such as <datasourcename>, <rulename>, or <statistic>, which DBmarlin replaces at send time. You can adapt them freely — for example set a different severity, change the summary, or add your own fields. Extra fields show up as custom details on the ilert alert.

When an alert rule fires, DBmarlin renders the matching template and posts it to ilert, which creates an alert.

FAQ

Will alerts in ilert be resolved automatically?

Yes, for alert rules that send the eventType field: ilert resolves the corresponding alert as soon as DBmarlin sends the event with eventType set to ended. This field is part of the host content template. If you also want database instance alerts to resolve automatically, add "eventType": "<startedended>", to the content template.

The ilert alert does not link back to DBmarlin. What is wrong?

Check the DBmarlin URL field of the webhook. It must be a URL that your responders can actually reach — http://localhost:9090 only works on the DBmarlin host itself, so use the externally reachable hostname of your DBmarlin installation instead.