squakez commented on PR #17389: URL: https://github.com/apache/camel/pull/17389#issuecomment-2710122828
> @squakez let me see if I got it correctly.... The developer would implement a listener that would be called for every log eip or log > component call in order to set the mdc. If so, the developer should be aware that if getting the MDC data is an expensive operation, it should be cached. Usually with MDC we set the parameters only once per thread. Hello @lsergio. No, the developer is not required to do any low level development. The idea is quite the opposite. Basically, if we agree on this design, the developer will just need to include any information he/she wants to include into the Exchange (ie, an header). The framework will take care to include this into the context, hence, any logging trace will contain the MDC variables. The framework will be in charge to clear it as well. Again, the idea of this (or any alternative approach) is to give the user a consistent way of using the feature in every DSL and without requiring to know the low details of the core or even the Java language. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
