We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I found this issue in the openshift-logging platform and traced it back to this component.
My example query of { kubernetes_namespace_name="some-namespace" } | json | level = "error" fails with the error
{ kubernetes_namespace_name="some-namespace" } | json | level = "error"
parse error at line 1, col 2002: syntax error: unexpected STRING
Tracing back lead me to the label enforcer, which somehow corrupts this query. In the debug logs i found that the query:
{log_type=~".+", kubernetes_namespace_name=~"<injected namespaces>"} | json | "error|err|eror"
is being sent upstream, meaning that we're losing the level field selector somewhere.
level
Hope I'm in the right place, but I'm not sure how to debug this further.
The text was updated successfully, but these errors were encountered:
cc @periklis
Sorry, something went wrong.
You are looking probably at this fix: #422 422
No branches or pull requests
I found this issue in the openshift-logging platform and traced it back to this component.
My example query of
{ kubernetes_namespace_name="some-namespace" } | json | level = "error"
fails with the errorTracing back lead me to the label enforcer, which somehow corrupts this query. In the debug logs i found that the query:
is being sent upstream, meaning that we're losing the
level
field selector somewhere.Hope I'm in the right place, but I'm not sure how to debug this further.
The text was updated successfully, but these errors were encountered: