Skip to content
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.

Feature Request: Configure container monitoring rules via Operator #338

Open
TimGerlach opened this issue Nov 2, 2020 · 5 comments
Open

Comments

@TimGerlach
Copy link

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.

@DTMad
Copy link
Member

DTMad commented Nov 6, 2020

@mreider - what do you think?

@Dant3s
Copy link

Dant3s commented Nov 12, 2020

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.

@PatrikSteuer
Copy link

Hi,
using a kubernetes native approach for dynatrace configuration would reduce the time to value of dynatrace in the k8s ecosystem.

@mreider
Copy link
Contributor

mreider commented Nov 16, 2020

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.

@mreider
Copy link
Contributor

mreider commented Nov 19, 2020

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants