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
{{ message }}
This repository has been archived by the owner on Jan 21, 2024. It is now read-only.
hi, thanks for developing the json-logger component.
I want to use json-logger in a RTF/EKS environment. I have EKS setup to forward the logs off to cloudwatch which works well. Currently the logs still come out in a stringified format, ie..
[2021-09-23 16:15:05.048] INFO JsonLogger [[MuleRuntime].uber.05 .... { json-logger.json }
I'd like to be able to alter the log4j2 format to be JSON format so that cloudwatch (or any other log parser) can parse it efficiently. either displaying only the json-logger json in the logs, or use the log4j2 json/gelf layout. Currently it looks like there is no way to override the log4j2.xml file in RTF.
Using json-logger, I guess it's possible to send the log messages to amq or some other service, this seems alright but IMO not as efficient as switching the entire log output to JSON.
As the contributors of this json-logger I figured you might have some good ideas on how to get a JSON only output format in the RTF logs?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
hi, thanks for developing the json-logger component.
I want to use json-logger in a RTF/EKS environment. I have EKS setup to forward the logs off to cloudwatch which works well. Currently the logs still come out in a stringified format, ie..
[2021-09-23 16:15:05.048] INFO JsonLogger [[MuleRuntime].uber.05 .... { json-logger.json }
I'd like to be able to alter the log4j2 format to be JSON format so that cloudwatch (or any other log parser) can parse it efficiently. either displaying only the json-logger json in the logs, or use the log4j2 json/gelf layout. Currently it looks like there is no way to override the log4j2.xml file in RTF.
Using json-logger, I guess it's possible to send the log messages to amq or some other service, this seems alright but IMO not as efficient as switching the entire log output to JSON.
As the contributors of this json-logger I figured you might have some good ideas on how to get a JSON only output format in the RTF logs?
The text was updated successfully, but these errors were encountered: