You're right—this applies at the namespace level. However, you can always leverage automatic tagging to fine-tune control.
A good approach is to create a global automatic tag rule (e.g., monitoring=true) and configure alerting or SLO evaluations to only apply when this tag is present. For workloads or namespaces that should be excluded, simply omit this tag.
Additionally, to increase reliability and avoid dependency on automatic rules (which may occasionally fail or be delayed), you can define the tag directly as an annotation within your Kubernetes workloads. This makes the tag native and persistent, ensuring consistent behavior regardless of the Dynatrace rules engine.
This provides a scalable way to manage what gets monitored or alerted on—without impacting the whole environment.
fuelled by coffee and curiosity. ☕
