rmannibucau commented on issue #8321: URL: https://github.com/apache/hop/issues/8321#issuecomment-5656121302
> 15 years sounds wrong but it could be true started to work (and java) in 2010 and it was already the case ;). that said the point is just it is mature (didnt mean anything else). otel is great when you do nothing crazy but it is lost as soon as you do something async so I wouldn't rely on pure automatic instrumentation on the long run - short term it is an insanely great move forward. sadly we can't rely on ebpf or alike for some internals/steps so fear instrumentation will need to be manual, logger based or not. @hansva 1. ack, i'm fine if we do target next minor instead of patch release 2. and 3. will look 4. think it is ok since row is insanely slower so this is negligible, also note it depends a lot on the binding and config, log4j2 is the consistent one with the stack and most powerful but not the fastest 5. exactly but this one is a goal too ;), let the deployer/packager decide > and we are not gaining much. The things you need can be done by rewriting the Slf4jLoggingEventListener and adding MDC in there. hmm not really until i enable to disable the appender which can be another option but keeps 2 competing coding pattern which is very error prone -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
