mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-22 22:27:47 -04:00
512bfebc10
Part of #84369. Implement the `Tracer` interface by providing a module that uses OpenTelemetry, along with Elastic's APM agent for Java. See the file `TRACING.md` for background on the changes and the reasoning for some of the implementation decisions. The configuration mechanism is the most fiddly part of this PR. The Security Manager permissions required by the APM Java agent make it prohibitive to start an agent from within Elasticsearch programmatically, so it must be configured when the ES JVM starts. That means that the startup CLI needs to assemble the required JVM options. To complicate matters further, the APM agent needs a secret token in order to ship traces to the APM server. We can't use Java system properties to configure this, since otherwise the secret will be readable to all code in Elasticsearch. It therefore has to be configured in a dedicated config file. This in itself is awkward, since we don't want to leave secrets in config files. Therefore, we pull the APM secret token from the keystore, write it to a config file, then delete the config file after ES starts. There's a further issue with the config file. Any options we set in the APM agent config file cannot later be reconfigured via system properties, so we need to make sure that only "static" configuration goes into the config file. I generated most of the files under `qa/apm` using an APM test utility (I can't remember which one now, unfortunately). The goal is to setup up a complete system so that traces can be captured in APM server, and the results in Elasticsearch inspected. |
||
|---|---|---|
| .. | ||
| elastic-apm-agent-1.33.0.jar.sha1 | ||
| elastic-apm-agent-LICENSE.txt | ||
| elastic-apm-agent-NOTICE.txt | ||
| opentelemetry-api-1.15.0.jar.sha1 | ||
| opentelemetry-context-1.15.0.jar.sha1 | ||
| opentelemetry-LICENSE.txt | ||
| opentelemetry-NOTICE.txt | ||
| opentelemetry-semconv-1.15.0-alpha.jar.sha1 | ||