Currently, deprecation logging logs only the timestamp and the deprecation message. For deployments with different application clients accessing Elasticsearch, it will be helpful to include some "origin" information such as the originating client host/ip in these messages. This way, admins can quickly identify the offending application(s) and reach out to the appropriate team(s) for remediation.
Currently, deprecation logging logs only the timestamp and the deprecation message. For deployments with different application clients accessing Elasticsearch, it will be helpful to include some "origin" information such as the originating client host/ip in these messages. This way, admins can quickly identify the offending application(s) and reach out to the appropriate team(s) for remediation.