Hi -
Thanks for getting back to me so quickly - it's not a blocker, more of
a question. Apologies for the long answer
There's no special message content, and I had a (messy, admittedly,
but small CamelCustomLogMask) workaround for XML. The workaround used
the default implementation, and
Hi
Log masking is only a best effort. What kind of message content do you
have, can you post an example.
Also tell us what Camel version you use. And try with the latest release
also.
If you have a very special message content then you can also implement your
own message formatter and do your
Hello,
When masking is enabled on a log statement that formats the entire
exchange, patterns used to identify message type (e.g.
source.startsWith("<")) fail, and the whole message body is logged.
I am unsure if this is a known issue, of I have configured masking incorrectly.
Best regards
