-
Notifications
You must be signed in to change notification settings - Fork 14
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
Detected field values: Response sometimes has space between digits and units, breaking queries #910
Comments
So this might be a bit more work then I was hoping in the frontend. We'll need to store the fieldType (e.g. bytes, float, duration, etc) in the JSON encoded value for the ad-hoc filter (like we currently store the parser) to only strip out white-space when the field is of type duration or bytes. |
We're going to push on a Loki side change grafana/loki#15052 instead of needing to encode the field type with every field value for now. |
so, after digging into this a bit more, I'm not sure what the desired behavior is? the response will reflect whatever the raw data has. if there's a space before the unit in the raw data, that's what we'll return. is the preference to be changing people's log lines, or should we look for a way to honor whichever way they've chosen to express the value in their log lines? |
If the response returns whatever the user has in the raw data, then that needs to be queryable in Loki, right now querying |
Fixed by grafana/loki#15272, which will be released in loki |
It will go out in |
Sometimes we get responses like this:
And other times like this:
Currently the spaces before the unit is making it into the query, which breaks the query as that is not valid logQL.
Please strip out white-spaces before the units and bring up to Loki folks to make sure this isn't a bug Loki side.
The text was updated successfully, but these errors were encountered: