Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loki doesn't create _extracted label suffix if there is more than one parser #12800

Open
KimMJ opened this issue Apr 26, 2024 · 1 comment
Open
Labels
type/bug Somehing is not working as expected

Comments

@KimMJ
Copy link

KimMJ commented Apr 26, 2024

Describe the bug
If the log has multiple depths and overlapping labels are encountered by a later parser, they will be ignored instead of creating labels with the _extracted suffix.

To Reproduce
Steps to reproduce the behavior:

  1. Loki version 2.9.4
  2. Log message:
    {"destination":"common","filepath":"/logs/envoy/current.log", "level":"INFO","log":"2024-04-26T08:52:04.746547Z\twarn\tEOF","timestamp":"2024-04-26T08:52:05.450Z"}
    
  3. Query: {<stream_selector>} | json | line_format "{{.log}}" | pattern "<time>\t<level>\t<message>"

Expected behavior

I exptected to see level=warn label kv, but it wasn't and there is no level_extracted label neither

Environment:

  • Infrastructure: Kubernetes (EKS 1.28)
  • Deployment tool: jsonnet
  • Version: 2.9.4
@JStickler JStickler added the type/bug Somehing is not working as expected label Apr 29, 2024
@timansky
Copy link

timansky commented May 14, 2024

Same bug with 3.0.0 version and level field in json

screen

Infrastructure: Kubernetes (vanila 1.28)
Deployment tool: manual
Version: 3.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Somehing is not working as expected
Projects
None yet
Development

No branches or pull requests

3 participants