Open iorfix opened 4 years ago
For some more context, this follows our discussion in https://discuss.elastic.co/t/api-key-name-as-additional-field-in-apm-server-data/230566/3.
@iorfix thanks for opening, we'll discuss priorities and possible solutions here.
We should consider aligning with the set_security_user
ingest processor https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest-node-set-security-user-processor.html.
Add Name Key information as additional parameter when API key are enabled. This parameter may help to trust apm agents on Elastic, in the same way as ssl_peer_metadata do in Logstash. As an example, an Elastic ingest pipeline could match service.name with apikey.name.