How to completely disable/hide alerting for a specific namespace/pattern?

[lictw]

Hey everyone! 👋

We’re not just looking to mute notifications. We want to completely hide these alerts and incidents from the UI. Ideally, Coroot should just ignore this pattern entirely and not generate any alerts or incidents for it in the corresponding tabs.

Is this currently possible, or are there any workarounds? Thanks!

[kgeminicdev]

There's no single "ignore this namespace" switch today. Category notification settings only suppress the notification; the alert or incident is still created. You can get close with these:

Alerts. Alerting rules select apps by all, category, or applications (glob). There's no "exclude" option, and every built-in rule uses all. Put the noisy apps in their own category (pattern noisy-ns/* or the coroot.com/application-category annotation). Then switch the rules to type: category and list every category except that one. Doing it in config is easiest: click Export on the Alerting Rules page and patch each built-in rule by id:

alertingRules:
  - id: memory-pressure
    selector:
      type: category
      categories: [application, production]   # everything except "noisy"

Incidents. These come from the Availability and Latency SLOs and don't look at categories. Disable both SLOs for those apps, either per app in the UI or with annotations:

annotations:
  coroot.com/slo-availability-objective: "0%"
  coroot.com/slo-latency-objective: "0%"

Hiding. The Incidents page has the category filter, so you can uncheck the category there. The Alerts list doesn't filter by category.

Not collecting at all. coroot-node-agent supports --container-denylist (env CONTAINER_DENYLIST), regexes matched against container IDs like /k8s/<namespace>/<pod>/<container>, for example .+/noisy-ns/.+. You lose all node-agent telemetry for those containers, not just the alerting.

A native exclude selector would be a reasonable feature request.