topic Re: kubernetes logmonitoring - log-ingest-rule-hierarchy (back to front) in Container platforms

Kubernetes log monitoring with log-ingest-rule-hierarchy (back to front)

gopher — Wed, 17 Dec 2025 12:06:10 GMT

Hi,
I'm currently implementing the Kubernetes log streaming via the "logs module" in Dynatrace. Doing this since we have recently moved from Full Stack to Application + Kubernetes monitoring and logs can't be collected in this format.

I've got it working this isn't the issue, the problem I'm facing is that the log-ingest-rule-hierarchy is back to front.
https://docs.dynatrace.com/docs/shortlink/lma-logs-from-kubernetes#log-ingest-rule-hierarchy

"Log ingest rules can be defined on environment scope but also on more fine-grained level like Kubernetes cluster. The matching hierarchy is as follows:

Host configuration rules;
Kubernetes cluster configuration rules;
Host group configuration rules;
Environment configuration rules "

The problem I am facing is that on deployment of the logging module, a Kubernetes cluster level rule is automatically created which has a default rule of collect all (every log on the cluster).

This then overwrites all other configurations (in particular the Environment) due to log-ingest-rule-hierarchy. This is back to front from the way that the Full Stack / OneAgent log collection works.

I do not want to have to create individual configurations per cluster as this is counter intuitive and a significant time-wasting exercise of massive #dynatoil.

Has anyone faced this? got any idea? or am I going to have to spend countless hours with dynatrace support on this.

Re: kubernetes logmonitoring - log-ingest-rule-hierarchy (back to front)

Michal_Gebacki — Tue, 16 Dec 2025 15:19:09 GMT

Hello, @gopher!

How this issue went further? Did you make any progress?

Thank you for any feedback!

Re: kubernetes logmonitoring - log-ingest-rule-hierarchy (back to front)

gopher — Tue, 16 Dec 2025 22:02:07 GMT

HI @Michal_Gebacki ,
Unfortunately, not, we have raised this through our accounts team back to PO and that's about it unfortunately.
Just another painful, half thought out implementation that adds to the list of reasons why we should continue using alternate logging methods other than Dynatrace (which are already in place).
Thanks

Re: Kubernetes log monitoring with log-ingest-rule-hierarchy (back to front)

mattb0m — Thu, 29 Jan 2026 16:53:50 GMT

We have also noticed this behavior, which we simply consider a bug. We may apply config on the cluster level with Terraform, but this implementation is clearly harmful.

Re: Kubernetes log monitoring with log-ingest-rule-hierarchy (back to front)

mattb0m — Thu, 29 Jan 2026 17:06:13 GMT

I have opened a product idea, as that is the only suolution Support ever propose for broken features :
https://community.dynatrace.com/t5/Product-ideas/Correct-k8s-Log-Monitoring-module-pushing-Log-Ingest-rules-per/idi-p/293878#M56192