Agent traces config for automatic_logging with log_instance backend is auto injecting label (traces: root), how to labeldrop or how can we get rid of such custom labels auto injected by agent

[chanrakanth-sivaraj]

Agent traces config for automatic_logging with log_instance backend is auto injecting label (traces: root), how to labeldrop?

This is causing issues when agent logs are blocking labels, that doesn't follow best practices.
The reason we have decided to block all labels not explicitly allowed by us is that the labels attached to the log affect how we store and index those logs which in turn affects the performance when querying for logs. By being stricter here on what we allow we ensure that our system remains performant and means we can stick to the best practices outlined by Loki themselves regarding labels (a couple of references for this, https://grafana.com/docs/loki/latest/best-practices/ and https://grafana.com/blog/2020/08/27/the-concise-guide-to-labels-in-loki/).

Sample detected fileds that auto injects traces label:

Agent traces config with log_instance backend :

[chanrakanth-sivaraj]

The worst part is Loki introduces best practices and Tempo violates, though products being from same organization. It seems weird when we see gaps between different products not aligned within the organization, when it is publically available.