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

[Log Parsing Pipelines] Filters referencing resources.* fields don't work #3884

Closed
raj-k-singh opened this issue Nov 3, 2023 · 0 comments · Fixed by #3889
Closed

[Log Parsing Pipelines] Filters referencing resources.* fields don't work #3884

raj-k-singh opened this issue Nov 3, 2023 · 0 comments · Fixed by #3889
Assignees

Comments

@raj-k-singh
Copy link
Collaborator

raj-k-singh commented Nov 3, 2023

When trying pipelines with filters like resources.service_name = some-service, if the actual logs have nil resources, collector logs end up being spammed with logs like

"2023-11-02T18:27:59.697Z warn router/router.go:119 Running expression returned an error {"kind": "processor", "name": "logstransform/pipeline_test", "pipeline": "logs", "operator_id": "router_signoz", "operator_type": "router", "error": "cannot fetch service_name from <nil> (1:11)\n | resources.service_name == \"some-service\"\n | ..........^"}"

Also the larger issue here is that even though the Signoz log model has a resources field, the field does not seem to be available on plog data structure provided to logtransform processor by the collector

@raj-k-singh raj-k-singh self-assigned this Nov 3, 2023
@raj-k-singh raj-k-singh changed the title [Log Parsing Pipelines] qbfiltertoexpr should generate paths with ?. separator [Log Parsing Pipelines] Filters referencing resources.* fields don't work Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant