Add trace ids to deprecation logs


I've noticed that your search and indexing slow logs have attached trace ids [Github code].

I was wondering if it would be possible to add them to deprecation logs as well?

The motivation behind this is the fact that we find it hard to remove deprecated features without knowing what is the source that is triggering them. We are using a micro-service infrastructure, where multiple services are hitting ES. Having trace ids in these deprecation logs would help us identify faster which service is triggering the deprecated feature.

Let me know what you think.


If not, is there a way to configure the deprecation logger to throw instead of log? Then, we would catch these exceptions in our service, where we have trace ids.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.