Is your feature request related to a problem? Please describe
Currently OpenSearch does not provide a clear way to assign a unique id per request.
We have X-Opaque-Id as part of header, but seems like it is not recommended to have it as an unique value per request. See here. Seems like it is meant to "label" request with something like clientId or similar (as it meant to deduplicate deprecation warning logs), so that the number of requests can be grouped/labelled together.
So if we can't use X-Opaque-Id, we will need another way via which users can pass a unique-id and which can be traced across multiple components for debugging purposes.
Describe the solution you'd like
Add support for something like X-Request-Id in the header to uniquely identify a request. Considering we already have distributed tracing framework, maybe we can use the same id to generate traces?
Related component
No response
Describe alternatives you've considered
No response
Additional context
No response
Is your feature request related to a problem? Please describe
Currently OpenSearch does not provide a clear way to assign a unique id per request.
We have
X-Opaque-Idas part of header, but seems like it is not recommended to have it as an unique value per request. See here. Seems like it is meant to "label" request with something like clientId or similar (as it meant to deduplicate deprecation warning logs), so that the number of requests can be grouped/labelled together.So if we can't use
X-Opaque-Id, we will need another way via which users can pass a unique-id and which can be traced across multiple components for debugging purposes.Describe the solution you'd like
Add support for something like
X-Request-Idin the header to uniquely identify a request. Considering we already have distributed tracing framework, maybe we can use the same id to generate traces?Related component
No response
Describe alternatives you've considered
No response
Additional context
No response