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.
