DBmarlin for ilert

DBmarlin spots the database problem. ilert makes sure the right person hears about it.

Database alerts that reach a person

DBmarlin alert rules send straight into ilert, where your escalation policy and on-call schedule take over. The engineer on duty is reached by push, SMS, voice call or chat, and if nobody acknowledges, ilert escalates on its own. A database problem at two in the morning stops depending on whether anyone happened to be looking at a dashboard.

Straight from the page to the problem

Every alert DBmarlin sends carries a deep link back into DBmarlin. Whoever picks up the page lands on the instance and the time window where the problem is happening, rather than on a front page with the investigation still ahead of them.

Alerts that close themselves

When the condition clears, DBmarlin tells ilert and the alert resolves. What is open in ilert reflects what is actually wrong, so nobody spends Monday morning tidying up a list of alerts that fixed themselves days ago.

Databases and hosts both covered

Alert on database statistics such as query time and execution counts, and on host statistics including CPU and disk utilisation. Rules support separate Info, Warning and Critical thresholds, so the same rule can nudge you early and escalate properly when it matters.

Set up in minutes, with no agent

The integration runs over DBmarlin's webhook, so there is nothing to install. Create a DBmarlin alert source in ilert, copy the webhook URL into DBmarlin under Settings and Integrations, and attach it to your alert rules. Make it the default and every rule uses it.

Full setup guide on docs.ilert.com