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
Describe the bug
We have Java applications where multiple threads are emitting exactly the same log body at exactly the same time (time granularity is ms). The OpenTelemetry resource attribute thread.name is set and used to distinguish between the 2 logs. However, it looks like, since they have the same timestamp and log body, Loki only takes 1 of the 2 logs entries and drop the other one (kind of a de-duplication which is not taking into account the structured metadata).
To Reproduce
Steps to reproduce the behavior:
Started Loki (3.2.0)
Push 1 log using the otlp endpoint. I have attached the logs I used for testing.
Push another log using the otlp endpoint with the same body, attributes and timestamp, just change the thread.name resource attribute.
Query: {service_name="duplicates.tests"} term. I tried this query with both Grafana and logcli
Only 1 of the 2 logs is returned
Expected behavior
2 logs lines returned with different values for thread_name structured metadata.
Environment:
Infrastructure: Kubernetes
Deployment tool: helm
Screenshots, Promtail config, or terminal output log.json
The text was updated successfully, but these errors were encountered:
Describe the bug
We have Java applications where multiple threads are emitting exactly the same log body at exactly the same time (time granularity is
ms
). The OpenTelemetry resource attributethread.name
is set and used to distinguish between the 2 logs. However, it looks like, since they have the same timestamp and log body, Loki only takes 1 of the 2 logs entries and drop the other one (kind of a de-duplication which is not taking into account the structured metadata).To Reproduce
Steps to reproduce the behavior:
thread.name
resource attribute.{service_name="duplicates.tests"} term
. I tried this query with both Grafana andlogcli
Expected behavior
2 logs lines returned with different values for
thread_name
structured metadata.Environment:
Screenshots, Promtail config, or terminal output
log.json
The text was updated successfully, but these errors were encountered: