You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Pasquale Congiusti <pa...@gmail.com> on 2026/03/05 08:09:50 UTC

Deprecate older tracing and MDC components in 4.19?

Hi team,
in the past I've worked to introduce new components and provide a better
consistency for telemetry [1] and mdc logging [2]. I think these components
are now mature enough and we should evaluate the deprecation of the older
components that these new ones are planning to replace. In particular I
have these 2 issues:

https://issues.apache.org/jira/browse/CAMEL-22479
https://issues.apache.org/jira/browse/CAMEL-22477

If there is no objection, we can deprecate them, reminding the user to use
the newer components instead. I advocate not to remove before any major
upgrade though (5.x), unless force majeure such as vulnerabilities or
problems we won't be able to manage easily during the rest of 4.x
development cycles. Happy to read any feedback around this task.

Thanks for the collaboration,
Pasquale.

[1] https://camel.apache.org/components/4.18.x/others/telemetry.html
[2] https://camel.apache.org/components/4.18.x/others/mdc.html

Re: Deprecate older tracing and MDC components in 4.19?

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

I think its good to deprecate as we are on the way for all those major
upgrades as part of the SB4 effort and so on.

We can surely remove these before 5.x as that is many years out in the wild.
And Camel has always removed old deprecated components from time to time.

Especially when there is another component that is replacing it to use - in
fact if we were able to do this in a faster way,
then such work would sometimes just be in the same component, and end user
would need to migrate.

Nothing is set in stone forever.



On Thu, Mar 5, 2026 at 9:10 AM Pasquale Congiusti <
pasquale.congiusti@gmail.com> wrote:

> Hi team,
> in the past I've worked to introduce new components and provide a better
> consistency for telemetry [1] and mdc logging [2]. I think these components
> are now mature enough and we should evaluate the deprecation of the older
> components that these new ones are planning to replace. In particular I
> have these 2 issues:
>
> https://issues.apache.org/jira/browse/CAMEL-22479
> https://issues.apache.org/jira/browse/CAMEL-22477
>
> If there is no objection, we can deprecate them, reminding the user to use
> the newer components instead. I advocate not to remove before any major
> upgrade though (5.x), unless force majeure such as vulnerabilities or
> problems we won't be able to manage easily during the rest of 4.x
> development cycles. Happy to read any feedback around this task.
>
> Thanks for the collaboration,
> Pasquale.
>
> [1] https://camel.apache.org/components/4.18.x/others/telemetry.html
> [2] https://camel.apache.org/components/4.18.x/others/mdc.html
>


-- 
Claus Ibsen

Re: Deprecate older tracing and MDC components in 4.19?

Posted by Pasquale Congiusti <pa...@gmail.com>.
Thanks for the feedback received. Reported issue (CAMEL-23133)
<https://issues.apache.org/jira/browse/CAMEL-23133> will be available in
4.19. I will proceed with the deprecation activity as there is no other
objection.

Cheers,
Pasquale.

On Thu, Mar 5, 2026 at 1:25 PM Pasquale Congiusti <
pasquale.congiusti@gmail.com> wrote:

> Hi Laurent,
> thanks for reporting. I've just created an issue,
> https://issues.apache.org/jira/browse/CAMEL-23133, it should be
> relatively easy to work on that one. Feel free to report any other possible
> feature that is missing. In any case, a deprecation does not mean we drop
> the support immediately, so, if we discover something is missing while
> doing the migrations to the new components, we can do it along the way.
>
> Cheers,
> Pasquale.
>
> On Thu, Mar 5, 2026 at 12:41 PM BIHANIC, LAURENT <
> laurent.bihanic@worldline.com> wrote:
>
>> Hello,
>>
>> The new MDC Logging component does not offer the same features as
>> MDCUnitOfWork. Typically, it misses pattern support (
>> *mdc-logging-keys-pattern*) that allows avoiding painful header/property
>> enumerations on large projets.
>> Typically, when working with REST services with many custom HTTP headers
>> and path and query parameters, setting *camel.mdc.customHeaders* to "*"
>> would pollute logs with far too many MDCs.
>>
>> Are there any plans to bring sone kind of pattern matching to the MDC
>> Logging component ?
>>
>> Thank you,
>>
>> Laurent
>>
>>
>> Le 05/03/2026 à 09:09, Pasquale Congiusti a écrit :
>>
>> Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe.
>>
>> Hi team,
>> in the past I've worked to introduce new components and provide a better
>> consistency for telemetry [1] and mdc logging [2]. I think these components
>> are now mature enough and we should evaluate the deprecation of the older
>> components that these new ones are planning to replace. In particular I
>> have these 2 issues:
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCAMEL-22479&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351916911%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0py5gLuuWius1%2BcwQE9WEX0JEgPJyjE7PE7Bye079NI%3D&reserved=0 <https://issues.apache.org/jira/browse/CAMEL-22479>https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCAMEL-22477&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351943165%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GaH0EercYJa4%2F6%2B7ftzFW4%2BVxNKjnR0wLCH6agxqEn0%3D&reserved=0 <https://issues.apache.org/jira/browse/CAMEL-22477>
>>
>> If there is no objection, we can deprecate them, reminding the user to use
>> the newer components instead. I advocate not to remove before any major
>> upgrade though (5.x), unless force majeure such as vulnerabilities or
>> problems we won't be able to manage easily during the rest of 4.x
>> development cycles. Happy to read any feedback around this task.
>>
>> Thanks for the collaboration,
>> Pasquale.
>>
>> [1] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcamel.apache.org%2Fcomponents%2F4.18.x%2Fothers%2Ftelemetry.html&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351966813%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=sGoAK2S0MjV8u4bw3kb6cTGJ4QRXmIeSNxtNyfiChv8%3D&reserved=0 <https://camel.apache.org/components/4.18.x/others/telemetry.html>
>> [2] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcamel.apache.org%2Fcomponents%2F4.18.x%2Fothers%2Fmdc.html&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351987541%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Gl9LV3HAVSF4SaE6j%2BWi4cDrExfVs%2BDdycWi5ovA5E4%3D&reserved=0 <https://camel.apache.org/components/4.18.x/others/mdc.html>
>>
>>
>> --
>> Laurent Bihanic
>> Architecte
>> Worldline - MTS France
>> Tour Voltaire, 1 Place des Degrés, 92800 Puteaux, Francetel:+33.6.25.73.03.74 <+33.6.25.73.03.74>mailto:laurent.bihanic@worldline.com <la...@worldline.com>
>>
>>
>> Those who surrender freedom for security will not have, nor do they
>> deserve, either one. (Benjamin Franklin)
>>
>>
>> DISCLAIMER:
>> The opinions expressed are entirely my own and may not necessarily be
>> those of my employer.  Also, I am not now nor have I ever been a
>> lawyer.  My opinions are provided as-is with absolutely no warranty of
>> merchantability or fitness for any particular use.  Besides, you can't
>> prove I typed this.  No body saw me type this.  Who says I typed this?
>>
>>
>> Worldline, Cardlink, GoPay and Santeos are registered trademarks and
>> trade names owned by the Worldline Group. This e-mail and any documents
>> attached are confidential and intended solely for the addressee. It may
>> also be privileged. If you are not the intended recipient of this e-mail,
>> you are not authorized to copy, disclose, use or retain it. Please notify
>> the sender immediately and delete this e-mail (including any attachments)
>> from your systems. As e-mails may be intercepted, amended or lost, they are
>> not secure. Therefore, Worldline’s and its subsidiaries’ liability cannot
>> be triggered for the message content. Although the Worldline Group
>> endeavors to maintain a virus-free network, we do not warrant that this
>> e-mail is virus-free and do not accept liability for any damages, losses or
>> consequences resulting from any transmitted virus if any. The risks are
>> deemed to be accepted by anyone who communicates with Worldline or its
>> subsidiaries by e-mail.
>> Please consider the environment before printing, sending or forwarding
>> this email.
>>
>>

Re: Deprecate older tracing and MDC components in 4.19?

Posted by Pasquale Congiusti <pa...@gmail.com>.
Hi Laurent,
thanks for reporting. I've just created an issue,
https://issues.apache.org/jira/browse/CAMEL-23133, it should be relatively
easy to work on that one. Feel free to report any other possible feature
that is missing. In any case, a deprecation does not mean we drop the
support immediately, so, if we discover something is missing while doing
the migrations to the new components, we can do it along the way.

Cheers,
Pasquale.

On Thu, Mar 5, 2026 at 12:41 PM BIHANIC, LAURENT <
laurent.bihanic@worldline.com> wrote:

> Hello,
>
> The new MDC Logging component does not offer the same features as
> MDCUnitOfWork. Typically, it misses pattern support (
> *mdc-logging-keys-pattern*) that allows avoiding painful header/property
> enumerations on large projets.
> Typically, when working with REST services with many custom HTTP headers
> and path and query parameters, setting *camel.mdc.customHeaders* to "*"
> would pollute logs with far too many MDCs.
>
> Are there any plans to bring sone kind of pattern matching to the MDC
> Logging component ?
>
> Thank you,
>
> Laurent
>
>
> Le 05/03/2026 à 09:09, Pasquale Congiusti a écrit :
>
> Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe.
>
> Hi team,
> in the past I've worked to introduce new components and provide a better
> consistency for telemetry [1] and mdc logging [2]. I think these components
> are now mature enough and we should evaluate the deprecation of the older
> components that these new ones are planning to replace. In particular I
> have these 2 issues:
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCAMEL-22479&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351916911%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0py5gLuuWius1%2BcwQE9WEX0JEgPJyjE7PE7Bye079NI%3D&reserved=0 <https://issues.apache.org/jira/browse/CAMEL-22479>https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCAMEL-22477&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351943165%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GaH0EercYJa4%2F6%2B7ftzFW4%2BVxNKjnR0wLCH6agxqEn0%3D&reserved=0 <https://issues.apache.org/jira/browse/CAMEL-22477>
>
> If there is no objection, we can deprecate them, reminding the user to use
> the newer components instead. I advocate not to remove before any major
> upgrade though (5.x), unless force majeure such as vulnerabilities or
> problems we won't be able to manage easily during the rest of 4.x
> development cycles. Happy to read any feedback around this task.
>
> Thanks for the collaboration,
> Pasquale.
>
> [1] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcamel.apache.org%2Fcomponents%2F4.18.x%2Fothers%2Ftelemetry.html&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351966813%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=sGoAK2S0MjV8u4bw3kb6cTGJ4QRXmIeSNxtNyfiChv8%3D&reserved=0 <https://camel.apache.org/components/4.18.x/others/telemetry.html>
> [2] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcamel.apache.org%2Fcomponents%2F4.18.x%2Fothers%2Fmdc.html&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351987541%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Gl9LV3HAVSF4SaE6j%2BWi4cDrExfVs%2BDdycWi5ovA5E4%3D&reserved=0 <https://camel.apache.org/components/4.18.x/others/mdc.html>
>
>
> --
> Laurent Bihanic
> Architecte
> Worldline - MTS France
> Tour Voltaire, 1 Place des Degrés, 92800 Puteaux, Francetel:+33.6.25.73.03.74 <+33.6.25.73.03.74>mailto:laurent.bihanic@worldline.com <la...@worldline.com>
>
>
> Those who surrender freedom for security will not have, nor do they
> deserve, either one. (Benjamin Franklin)
>
>
> DISCLAIMER:
> The opinions expressed are entirely my own and may not necessarily be
> those of my employer.  Also, I am not now nor have I ever been a
> lawyer.  My opinions are provided as-is with absolutely no warranty of
> merchantability or fitness for any particular use.  Besides, you can't
> prove I typed this.  No body saw me type this.  Who says I typed this?
>
>
> Worldline, Cardlink, GoPay and Santeos are registered trademarks and trade
> names owned by the Worldline Group. This e-mail and any documents attached
> are confidential and intended solely for the addressee. It may also be
> privileged. If you are not the intended recipient of this e-mail, you are
> not authorized to copy, disclose, use or retain it. Please notify the
> sender immediately and delete this e-mail (including any attachments) from
> your systems. As e-mails may be intercepted, amended or lost, they are not
> secure. Therefore, Worldline’s and its subsidiaries’ liability cannot be
> triggered for the message content. Although the Worldline Group endeavors
> to maintain a virus-free network, we do not warrant that this e-mail is
> virus-free and do not accept liability for any damages, losses or
> consequences resulting from any transmitted virus if any. The risks are
> deemed to be accepted by anyone who communicates with Worldline or its
> subsidiaries by e-mail.
> Please consider the environment before printing, sending or forwarding
> this email.
>
>

Re: Deprecate older tracing and MDC components in 4.19?

Posted by "BIHANIC, LAURENT" <la...@worldline.com>.
Hello,

The new MDC Logging component does not offer the same features as MDCUnitOfWork. Typically, it misses pattern support (mdc-logging-keys-pattern) that allows avoiding painful header/property enumerations on large projets.
Typically, when working with REST services with many custom HTTP headers and path and query parameters, setting camel.mdc.customHeaders to "*" would pollute logs with far too many MDCs.

Are there any plans to bring sone kind of pattern matching to the MDC Logging component ?

Thank you,

Laurent


Le 05/03/2026 à 09:09, Pasquale Congiusti a écrit :

Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe.

Hi team,
in the past I've worked to introduce new components and provide a better
consistency for telemetry [1] and mdc logging [2]. I think these components
are now mature enough and we should evaluate the deprecation of the older
components that these new ones are planning to replace. In particular I
have these 2 issues:

https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCAMEL-22479&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351916911%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0py5gLuuWius1%2BcwQE9WEX0JEgPJyjE7PE7Bye079NI%3D&reserved=0<https://issues.apache.org/jira/browse/CAMEL-22479>
https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCAMEL-22477&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351943165%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GaH0EercYJa4%2F6%2B7ftzFW4%2BVxNKjnR0wLCH6agxqEn0%3D&reserved=0<https://issues.apache.org/jira/browse/CAMEL-22477>

If there is no objection, we can deprecate them, reminding the user to use
the newer components instead. I advocate not to remove before any major
upgrade though (5.x), unless force majeure such as vulnerabilities or
problems we won't be able to manage easily during the rest of 4.x
development cycles. Happy to read any feedback around this task.

Thanks for the collaboration,
Pasquale.

[1] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcamel.apache.org%2Fcomponents%2F4.18.x%2Fothers%2Ftelemetry.html&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351966813%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=sGoAK2S0MjV8u4bw3kb6cTGJ4QRXmIeSNxtNyfiChv8%3D&reserved=0<https://camel.apache.org/components/4.18.x/others/telemetry.html>
[2] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcamel.apache.org%2Fcomponents%2F4.18.x%2Fothers%2Fmdc.html&data=05%7C02%7Claurent.bihanic%40worldline.com%7C50ece0814fba41238caf08de7a8eab5e%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C639082950351987541%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Gl9LV3HAVSF4SaE6j%2BWi4cDrExfVs%2BDdycWi5ovA5E4%3D&reserved=0<https://camel.apache.org/components/4.18.x/others/mdc.html>




--
Laurent Bihanic
Architecte
Worldline - MTS France
Tour Voltaire, 1 Place des Degrés, 92800 Puteaux, France
tel:+33.6.25.73.03.74
mailto:laurent.bihanic@worldline.com


Those who surrender freedom for security will not have, nor do they
deserve, either one. (Benjamin Franklin)


DISCLAIMER:
The opinions expressed are entirely my own and may not necessarily be
those of my employer.  Also, I am not now nor have I ever been a
lawyer.  My opinions are provided as-is with absolutely no warranty of
merchantability or fitness for any particular use.  Besides, you can't
prove I typed this.  No body saw me type this.  Who says I typed this?



Worldline, Cardlink, GoPay and Santeos are registered trademarks and trade names owned by the Worldline Group. This e-mail and any documents attached are confidential and intended solely for the addressee. It may also be privileged. If you are not the intended recipient of this e-mail, you are not authorized to copy, disclose, use or retain it. Please notify the sender immediately and delete this e-mail (including any attachments) from your systems. As e-mails may be intercepted, amended or lost, they are not secure. Therefore, Worldline’s and its subsidiaries’ liability cannot be triggered for the message content. Although the Worldline Group endeavors to maintain a virus-free network, we do not warrant that this e-mail is virus-free and do not accept liability for any damages, losses or consequences resulting from any transmitted virus if any. The risks are deemed to be accepted by anyone who communicates with Worldline or its subsidiaries by e-mail.
Please consider the environment before printing, sending or forwarding this email.