Introducing Alert Policies: Pod & Namespace Filter Search
Released on: May 2026Atatus now supports granular pod and namespace filtering when creating Kubernetes alert rules, enabling teams to scope alerts precisely to specific workloads and eliminate noise from unrelated services running across the same cluster.
With this update, developers and DevOps teams can type a namespace or pod name directly into the Filter By field and select from a live autocomplete list of matching workloads, making it simple to create focused, actionable Kubernetes alerts without needing to remember exact pod names or write complex label selectors by hand.
Key Benefits of Kubernetes Alert Filtering in Atatus:
- Pod-Level Alert Precision: Scope any Kubernetes metric alert to one or more specific pods by name, eliminating noise from unrelated workloads sharing the same metric across the cluster.
- Namespace-Aware Scoping: Filter by namespace first to narrow the pod search space, making rule creation fast and accurate even in clusters with hundreds of workloads spread across multiple teams.
- Live Autocomplete Dropdown: As you type, a real-time dropdown surfaces matching pod instances from your live cluster, no need to remember exact pod names or generated hash suffixes.
- Works Across All Kubernetes Metric Types: The same filter UI applies whether you are alerting on Pod metrics, Container metrics, Node metrics, Deployment metrics, or any of the 15+ supported Kubernetes metric dimensions.
- Dramatically Reduced Alert Fatigue: Targeted, workload-specific rules mean on-call engineers receive only the notifications they can act on immediately, rather than broad cluster-wide noise that is hard to action.
Monitor your software stack for free with Atatus.
Start your free trialOR
Request a DemoFree 14-day trial. No credit card required. Cancel anytime.