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
I have a job that runs AWS Nuke weekly. It outputs logs in the standard format, which is good for reviewing the results because it is human-readable. But sometimes I want to do some analysis on the results which is much easier when the logs are in JSON format.
I'd like to keep the stdout logs as-is but be able to also specify a file to write logs to (either in JSON format, or in a configurable format).
The text was updated successfully, but these errors were encountered:
@apgrucza interesting idea, I'm not sure the current logging system can handle that, I do have some tentative plans to overhaul it but not anytime soon.
How are you thinking this would work? We'd need a way to state output to stdout and output to a log file or is stdout always a thing and you can just specify an additional output and format?
I have a job that runs AWS Nuke weekly. It outputs logs in the standard format, which is good for reviewing the results because it is human-readable. But sometimes I want to do some analysis on the results which is much easier when the logs are in JSON format.
I'd like to keep the stdout logs as-is but be able to also specify a file to write logs to (either in JSON format, or in a configurable format).
The text was updated successfully, but these errors were encountered: