You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.
Hi,
we would like to configure container monitoring rules via the Dynatrace operator config. Currrently, container monitoring rules can only be configured via the Dynatrace UI which doesn't allow us to automate these configuration. For example, due to some known issues, we'd like to disable deep monitoring for the kube-system namespace.
The text was updated successfully, but these errors were encountered:
Hi,
we had a client today that asked if this is possible. The objective is be able to automate the injection with out touching the UI. In our case via labels or annotations, from the operator config.
It looks like there is no Dynatrace API endpoint for container monitoring rules. So we should start there. After this is possible, we can think about linking this with the Operator somehow. We want to avoid having two, potentially conflicting, places to save these rules.
I have confirmed that container monitoring rules will be available with our "settings 2.0" launch early next year. We will also figure out how to make this compliment / functional with our new flexible injection, via admission controller. That will be later on in the year, however.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
we would like to configure container monitoring rules via the Dynatrace operator config. Currrently, container monitoring rules can only be configured via the Dynatrace UI which doesn't allow us to automate these configuration. For example, due to some known issues, we'd like to disable deep monitoring for the
kube-system
namespace.The text was updated successfully, but these errors were encountered: