Skip to content

View Logs button applies message body filter from base query #1166

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

Open
aven-mathew opened this issue Feb 14, 2025 · 0 comments
Open

View Logs button applies message body filter from base query #1166

aven-mathew opened this issue Feb 14, 2025 · 0 comments

Comments

@aven-mathew
Copy link

aven-mathew commented Feb 14, 2025

What happened:
When clicking on the "view logs" button when a filter on the message content is defined in explorer the trace logs inherits the message filter.

What you expected to happen:
This seems like unexpected behavior since all other filters are not transferred to the trace log view and in our case generally is a hindrance when we want to view the full logs for the trace quickly. Ideally, this message filter would either not be propagated by default (as is the case with other filters) or would be able to not be propagated by a feature flag. It looks like the propagation occurs due to the meta field logMessageLike.

How to reproduce it (as minimally and precisely as possible):
Start a OTEL logs query with a message filter.
Click "view logs" on a message that has a trace with more than that message
See that the trace is also filtered by the message body filter.

Environment:

  • Grafana version: 11.4.1
  • Plugin version: 4.7.0
  • OS Grafana is installed on: k8s/helm deploy
  • User OS & Browser: chrome
  • Others:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Incoming
Development

No branches or pull requests

2 participants