[ML] Add request origin to the EIS X-elastic-product-use-case header #135513
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
X-elastic-product-use-case
is change to be a multi-value header and the request origin (search, ingest, unspecified) added to the header for sparse and dense embedding requests. Clients can also setX-elastic-product-use-case
which is why it must be a multi-value header.The 3 potential values are
unspecified
requests come directly from the REST APINon issue as it relates to internal comms between Elasticsearch and the Elastic Inference Service