Skip to content

Built-in rules

Every integration that needs one ships built-in rules: the rules its events follow until you change them (see each source’s own page for what its built-in rules actually do — Proxmox, Uptime Kuma, Alertmanager/Grafana, Gotify-compatible, Pulse, NetAlertX, Checkmate, the InfraInbox watcher). A built-in rule only routes an event — it can never change a severity or a title, unlike a rule of your own.

Built-in rules are Routing’s Built-in rules section (Notifications → Routing): one line per integration you have a source for (“Proxmox · 6 rules”), the sources they apply to (“Applies to test-proxmox, homelab-pve” — editing them changes all of these), whether they are as shipped or edited, and Update available when a newer version ships; the integrations you have no source for are folded under Other integrations (N). Click a line to read its rules as rows:

When Outcome Notify Closes
Backup and PBS job failures Opens an incident Default’s recipients After 20h without a new event, or on recovery
HA fencing Opens an incident Default’s recipients, repeating every 5m up to 6 times until acknowledged On recovery or by hand
Firing alerts (a rule that only sets how long its incident stays open) As Default decides As Default decides On recovery or by hand

Details under each rule shows the exact event types and conditions it matches. Edit rules opens their own page, where each rule shows its outcome and who it notifies, the same Details, its Closes after field, and Edit rule, which opens it in a panel on the right.

How built-in rules fit in with your own rules

Section titled “How built-in rules fit in with your own rules”

Your custom rules in Routing run first, top to bottom, exactly as always. Built-in rules run underneath them, scoped to the sources of that integration — so they only ever catch what your own rules didn’t already decide.

A built-in rule that tells “Default’s recipients” means whoever Default tells for the event’s severity, unless the source is on a rule for some sources with Also use these recipients for built-in alerts on: then that rule’s recipients stand in for them, in the built-in rules as shipped or edited.

Built-in rules can be edited at two levels:

  • Workspace — your own copy of the integration’s built-in rules, applied to every source of that integration.
  • Source — one source’s own copy, which overrides the workspace’s copy for that source alone. Useful when one cluster needs different tuning than its siblings, without touching everyone else.

Editing either copies the shipped rules into an editable set; it stops following future changes to what InfraInbox ships until you either edit again or reset it back.

Opening a source’s built-in rules copies nothing by itself: the save bar at the foot of the page appears only once you change something, and the first Save is what gives the source its own copy. In a rule’s editor, Apply puts your edit back into the set; nothing is written until you save the built-in rules. A rule with no route, one that only sets how long its incident stays open, keeps no route through an edit; picking one in its editor makes it decide where the events go. A save says Saved, with Undo for a few seconds. Opened from a source, the page’s back link and Save or Cancel return you to that source.

If InfraInbox updates an integration’s shipped built-in rules and you’ve made your own copy, the Built-in rules list flags it: Update available. Open it to see A newer version of these built-in rules is available, with what changed, rule by rule, and decide whether to bring the change in yourself — an edited copy never updates itself out from under you.

Reset to the built-in rules (workspace) or Remove this source’s copy (source) drops your own edits and goes back to following whatever InfraInbox ships.

  • Routing rules — your own rules, which always run first
  • Preview routing — check what a built-in rule (or your edit to one) actually does