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
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:
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: