- 
                Notifications
    
You must be signed in to change notification settings  - Fork 86
 
Description
Currently, there is a log Kamelet (action and sink):
- https://camel.apache.org/camel-kamelets/4.10.x/log-action.html
 - https://camel.apache.org/camel-kamelets/4.10.x/log-sink.html
 
Over time, this became a bit big, because of the number of parameters needed.
The questions are:
- How can the number of parameters be low to not overwhelm new users?
 - How can the number of parameters be complete to cater advanced users?
 
I would propose to split logging into 4 kamelets:
- Log
 - Log-quick
 - Log-data
 - Log-message
 
Details per Kamelet
- Log
 
This is the log Kamelet that most users can use. I would keep the number of parameters low (using a convention-over-configuration approach). This could be the parameters:
- level
 - name (loggerName)
 - showBody
 - showBodyType
 - showHeaders
 - showProperties
 
- Log-quick
 
This can be a Kamelet without parameters to quickly log something.
The URI could be
log:quick-log-action?showAll=true&multiline=true
If you want to provide some minimal parameters, then only provide level and name with good defaults.
- Log-data
 
This can be a Kamelet with most log parameters for advanced user. These are all the parameters of the current log Kamelet +
- plain
 - style
 - showCaughtException (formatting)
 - showException (formatting)
 - showExchangeId
 - showVariables
 
- Log-message
 
This Kamelet uses the log-eip (https://camel.apache.org/components/4.10.x/eips/log-eip.html) with the following parameters:
- level
 - name
 - language
 - message
 
In this way, these 4 Kamelets would cover most uses cases for most users.