You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elasticsearch supports passing in the x-opaque-id header to the tasks executing that search, for identification.
However, at the moment, we don't have a proper way of using it for any purpose (for example to associate search tasks with a Search Session), as the header is being over-written by core, for audit logging pirposes.
Ideally, we should be able to pass in and store multiple values using the x-opaque-id, so I believe we should discuss the details and implications of this approach.
The text was updated successfully, but these errors were encountered:
Elasticsearch supports passing in the
x-opaque-id
header to the tasks executing that search, for identification.However, at the moment, we don't have a proper way of using it for any purpose (for example to associate search tasks with a
Search Session
), as the header is being over-written bycore
, for audit logging pirposes.Ideally, we should be able to pass in and store multiple values using the
x-opaque-id
, so I believe we should discuss the details and implications of this approach.The text was updated successfully, but these errors were encountered: