You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logrus default of putting all logs on stderr makes administering Argo exceedingly difficult, as my log viewer in GCP believes every log coming from Argo is an Error. I'd like a way to configure Argo such that I can tell it to log to stdout instead of stderr.
Use Cases
Just about every day I'm looking at the Argo logs, and I'm currently debugging a production issue with Argo that is, so far, impenetrable because of the noise caused by every log event being marked as an Error.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
The logrus default of putting all logs on stderr makes administering Argo exceedingly difficult, as my log viewer in GCP believes every log coming from Argo is an Error. I'd like a way to configure Argo such that I can tell it to log to stdout instead of stderr.
Use Cases
Just about every day I'm looking at the Argo logs, and I'm currently debugging a production issue with Argo that is, so far, impenetrable because of the noise caused by every log event being marked as an Error.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: