Actually what my service do is to collect
stdout/stderr
from the Docker socket
That's exactly how the agent works, it cannot really filter it, it logs everything by default for full visibility ...
@Is there a way to choose other logs format ? to get a json or something like that?
or setting logging level?
send the agent's logs to log management and monitoring service,
These are stored into ELK, it was built to store large amounts of logs, I cannot see any reason why one would want to remove it?
Maybe if there would be a way to change their format, it could also help filtering them from my side.
You mean in the UI?
Maybe if there would be a way to change their format, it could also help filtering them from my side.
@<1523701205467926528:profile|AgitatedDove14> I am not sure if it would help but lets try 🙂
@<1523701205467926528:profile|AgitatedDove14> Actually what my service do is to collect stdout/stderr from the Docker socket. I meant to the stdout/stderr .
In the agent, no, it pipes stdout/stderr of the container and logs everything 😞
to get a json or something like that?
There is an api to get all the console logs, is this what you are after?
Hi @<1523701205467926528:profile|AgitatedDove14> , I send the agent's logs to log management and monitoring service, and we get big amount of info logs (especially if we use schedulers and launch agents again and again as part of the production pipeline). I think that it is important to set level also for other levels then debugging, WDYT?
@<1523701205467926528:profile|AgitatedDove14> Even if there is a way to set the format of those logs, that will be fine for now
Hi SmugTurtle78 , I'm not sure it's possible. Maybe SuccessfulKoala55 knows some workaround. Do you want to get rid of them in all scenarios or in just some specific use cases?
Hi CostlyOstrich36 ,Thanks for your answer, I would like it to be configurable , just like I set logging level for my logs.
Hi SmugTurtle78
Unfortunately there is no actual filtering for these logs, because they are so important for debugging and visibility. I have to ask, what's the use case to remove some of them ?