Include user information when Kibana sends an x-opaque-id
header to Elasticsearch
#178767
Labels
enhancement
New value added to drive a business result
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Describe the feature:
Today, Kibana includes an x-opaque-id header for search requests originating from Lens, Discover, Maps, and Alerting. This gets propagated in Elasticsearch's search slow logs and is helpful in identifying where a slow request originated from:
It'd be helpful to also include the user who submitted the request. Right now, we'd have to rely on Elasticsearch audit logs and match up
elasticsearch.slowlog.id
<-->opaque_id
to learn the user behind the request.Slow log:
Audit log:
The text was updated successfully, but these errors were encountered: