loguru support standout logging with json and csv #2415
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In a container deployment such as ECS and Kubernetes, the log should go to the standard out. The current log also has a leading timestamp, and line breakers. We would like to remove them and keep the log in a single line for any container based deployment.
Any container based deployment can set
container_csv
,container_json
orcontainer
in an env variableLANGFLOW_LOG_ENV
to override the default logging format.These are examples of json and csv based logging. The default behaviour of logging format is unchanged.