Supports #52125
Related #60119
We need to be able to correlate different logs in the regular system logger, Kibana's audit logs, and Elasticsearch's audit logs to the same user request.
When the X-Opaque-Id has been set on the request (for example, by a reverse proxy), we should:
- Forward this header to Elasticsearch
- This may already be solved by the
elasticsearch.requestHeadersWhitelist configuration option. This should be verified that this works.
- Include the identifier on any AuditTrail logs emitted during an HTTP request. This should automatically be bound via the request context.
Supports #52125
Related #60119
We need to be able to correlate different logs in the regular system logger, Kibana's audit logs, and Elasticsearch's audit logs to the same user request.
When the
X-Opaque-Idhas been set on the request (for example, by a reverse proxy), we should:elasticsearch.requestHeadersWhitelistconfiguration option. This should be verified that this works.