-
Notifications
You must be signed in to change notification settings - Fork 25
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
Remove Redundant logs #576
Comments
Thanks for sharing this issue, Peter. I'm happy to report that we have had this on our radar for a bit (VC-33564) and have started investigating. |
@hawksight We've made a few changes and discoveries which should address this problem.
|
@wallrj - thank you for detailed notes.
|
@hawksight Let's close this. We've fixed most of the redundant logs. Here's a jq filtering example, courtesy of Copilot:
Alternatively, you could just use grep and a series of file:line expressions e.g.
Another thing I forgot to mention is that we've also fixed the RBAC to allow the agent to list OpenShift routes and Firefly resources, so you should no longer see those |
Can we remove redundant logs about the
server missing resource for datagatherer
?It makes it very difficult to actually see logs that do mean something.
What happened?
Take a look at this snippet of logs:
What should had happened?
If the cluster doesn't have a resource, stop looking for it.
Or at the very least limit the logs about this 1 line only.
Worst case the agent is being a very bad citizen in the cluster continually polling the k8s API for things that just aren't there.
Possible fixes
I did previously try adding
--strict
but this seems to have no effect in my previous attempts.Log Filtering
I manually tried taking a small agent log and filtering out a bunch of log lines to see what diference it would make. Here's my resutls:
Here's my very quick commands:
I've attached both log fils here to see which you prefer to look at:
The text was updated successfully, but these errors were encountered: