-
Notifications
You must be signed in to change notification settings - Fork 279
Support log-level for controller logs #238
Comments
Hi @dorroddorrod , you can add spec:
template:
spec:
containers:
- command:
- applicationset-controller
- --debug # <-------- add this Or you can edit the install.yaml, add the line as above, and reapply using |
Hi @jgwest |
Ah, gotcha, sorry about that 😅, we don't have that currently, and the logs are definitely verbose by default. Let me convert this issue into an enhancement for that. |
Do we have any thoughts on how this should be implemented? Ie, instead of taking Accept 2 for backward compatibility? Any suggestions on which I am interested in completing this issue :) |
Awesome, thanks @rumstead. Exactly as you said, it couldn't hurt to keep Open to suggestions re: which info logs should be downgraded, if they are not providing any value. |
@jgwest feel free to assign to me |
Ok, so the majority of the logs are coming from the git clients in ArgoCD. The git client every time it runs a command -> hits this method -> which captures tracing spans Since it uses @jgwest any comments or suggestions here? You will see very similar logs in the
|
@rumstead, looks like we're stuck with those messages for now, without an upstream Argo CD patch to reduce their verbosity. |
Ok, the PR adds the scaffolding to support multiple log levels. |
@jgwest EDIT:
Enhancement Request:
Add support for configurable log levels via parameter, eg the ability to set additional log levels beyond just the
--debug
parameter support we have now. For example, as requested, ability to set the log level to only show error or warn.Original Text from @dorroddorrod
Hi,
Is there any way to control the log level for the application-set controller ?
The text was updated successfully, but these errors were encountered: