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 was archived by the owner on Jan 6, 2023. It is now read-only.
This is more of an enhancement request than a problem...
there is a need to support Logging for components on top of WebLogic, like Service Bus, Analytics Publisher and more.
Instead of using the default WebLogic Logger, one must be able to specify the Logger by name, like "oracle.osb".
The ODL format is different from standard WebLogic logging, almost like JSON with brackets around most of the items:
[timestamp] [component id] [messagetype:level] [message-id] [module id]
([field-name: field-value])* message-text [supplemental-detail]
The text was updated successfully, but these errors were encountered:
I will bring this to the attention of the FMW product PMs who are certifying their products in Kubernetes with the WebLogic ToolKit to capture this enhancement.
Thanks
Monica
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is more of an enhancement request than a problem...
there is a need to support Logging for components on top of WebLogic, like Service Bus, Analytics Publisher and more.
Instead of using the default WebLogic Logger, one must be able to specify the Logger by name, like "oracle.osb".
The ODL format is different from standard WebLogic logging, almost like JSON with brackets around most of the items:
[timestamp] [component id] [messagetype:level] [message-id] [module id]
([field-name: field-value])* message-text [supplemental-detail]
The text was updated successfully, but these errors were encountered: