Closed Homulvas closed 7 months ago
Thanks for the report @Homulvas 👍 We'll work out more uniform support of quoting and extend the CI to make sure its not missed
Hello @Homulvas . are you using the bun version?
Hello @Homulvas . are you using the bun version?
I originally installed it from the helm chart. I assume that uses the NodeJS runtime. Should I try bun instead?
@Homulvas I see the bug. Thanks for the issue.
Just for the information: using paremeterized json parser like | json resources_some_resource="resources.some_resource" | resources_some_resource!="something"
is highly encouraged as it works much faster than the parameterless json
parser
This becomes a bit of a usability issue then. I'm using Grafana with Loki source to query the logs and using the Grafana UI to filter based on the values from some log entry will not build a query using the parameterized json.
@Homulvas Anyway, the reported issue should be fixed in 3.2.6. Please recheck.
Got same error in 3.2.6 Stacktrace: https://gist.github.com/asvasyanin/13d305881fb033b39e4a231f41d46d23
@asvasyanin a bit different error. Will fix. Thanks for the report.
@asvasyanin fixed in 3.2.7
Closing as resolved. Feel free to reopen is needed 👍
Query
Results in a complete crash of the application with the following error:
I'm running
v3.2.4
The resource label might not exist on all the log entries
Changing the query to
{namespace="X"} | json resources_some_resource!="something"
makes it work but the first query is generated by the Grafana UI "Filter out value" selectors so there is absolutely no reason why it shouldn't work.