-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Cannot query logs from eventrouter with {name="eventrouter"} #940
Comments
@gouthamve Do you have any ideas? |
Hi @minhdanh, did you manage to fix this? I'm having the same problem |
It's normal that you get the JSON displayed like this. You can use a parser expression to extract labels. See https://grafana.com/docs/loki/latest/logql/#parser-expression Check out my demo which includes the eventrouter and also a dashboard for it. |
Hi, I just followed the sample code, used stdout as well, so nothing special. And if I do kubectl get logs form the eventrouter I do get nice log, starting with {"verb": etc... Is it something that I can change in loki config maybe? Thanks in advance |
I hope this helpful.
|
Thanks. I finally used promtail pipeline stage to do replace, to remove the first part of the log:
This left only the good log, which can later I passed through json parser (i think, as what they asked me to do later they said ,we don't need it), so with that i could easily search and filter per field |
@minhdanh I am facing the issue for scraping the kubernetes events logs to Grafana loki. I have |
I followed this blog post: https://grafana.com/blog/2019/08/21/how-grafana-labs-effectively-pairs-loki-and-kubernetes-events/
and installed eventrouter to the cluster (using the official helm chart) (to namespace
loki
).But now when I query loki using {name="eventrouter"}, loki is returning empty results. Although I can see the logs from the eventrouter pods:
I also tried to deploy eventrouter to
kube-system
namespace but that didn't change anything.Not sure what I'm doing wrong here.
The text was updated successfully, but these errors were encountered: