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
When running a query over JSON data that, when parsed, have detected labels that collide with existing index labels, the log lines will appear to be modified such that the JSON key is replaced with key_extracted. These additional 10 characters overwrite the next 10 characters in the log line, invariably causing the JSON to fail to parse.
The behaviour is not consistent when the query is run repeatedly, so sometimes these keys will not be corrupted and sometimes they will.
To Reproduce
Steps to reproduce the behavior: provided via internal Slack
Expected behavior
The log line to be returned as it was ingested into Loki, and successfully parsed by the JSON parser.
Environment:
Infrastructure: Kubernetes
Deployment tool: jsonnet
Screenshots, Promtail config, or terminal output
Provided via internal Slack
The text was updated successfully, but these errors were encountered:
Describe the bug
When running a query over JSON data that, when parsed, have detected labels that collide with existing index labels, the log lines will appear to be modified such that the JSON key is replaced with
key_extracted
. These additional 10 characters overwrite the next 10 characters in the log line, invariably causing the JSON to fail to parse.The behaviour is not consistent when the query is run repeatedly, so sometimes these keys will not be corrupted and sometimes they will.
To Reproduce
Steps to reproduce the behavior: provided via internal Slack
Expected behavior
The log line to be returned as it was ingested into Loki, and successfully parsed by the JSON parser.
Environment:
Screenshots, Promtail config, or terminal output
Provided via internal Slack
The text was updated successfully, but these errors were encountered: