observability-edot-java-instrument
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseEDOT Java Instrumentation
EDOT Java 埋点指南
Read the setup guide before making changes:
在进行修改前,请先阅读设置指南:
Guidelines
实施准则
- Use (download from GitHub releases, not a Maven/Gradle dependency)
elastic-otel-javaagent.jar - Attach via or
-javaagent:/path/to/elastic-otel-javaagent.jar— without this the agent does nothingJAVA_TOOL_OPTIONS="-javaagent:/path/to/elastic-otel-javaagent.jar" - Set exactly three required environment variables:
OTEL_SERVICE_NAME- — must be the managed OTLP endpoint or EDOT Collector URL. Never use an APM Server URL (no
OTEL_EXPORTER_OTLP_ENDPOINT, noapm-server, no:8200)/intake/v2/events - —
OTEL_EXPORTER_OTLP_HEADERSor"Authorization=ApiKey <key>""Authorization=Bearer <token>"
- Do NOT set ,
OTEL_TRACES_EXPORTER, orOTEL_METRICS_EXPORTER— the defaults are already correctOTEL_LOGS_EXPORTER - Never run both classic Elastic APM agent and EDOT agent on the same JVM
- 使用(从GitHub Releases下载,而非Maven/Gradle依赖)
elastic-otel-javaagent.jar - 通过或
-javaagent:/path/to/elastic-otel-javaagent.jar挂载Agent——不配置此参数的话,Agent将无法生效JAVA_TOOL_OPTIONS="-javaagent:/path/to/elastic-otel-javaagent.jar" - 必须设置以下三个必填环境变量:
OTEL_SERVICE_NAME- ——必须为托管式OTLP端点或EDOT Collector的URL。切勿使用APM Server URL(不能包含
OTEL_EXPORTER_OTLP_ENDPOINT、apm-server或:8200)/intake/v2/events - ——格式为
OTEL_EXPORTER_OTLP_HEADERS或"Authorization=ApiKey <key>""Authorization=Bearer <token>"
- 请勿设置、
OTEL_TRACES_EXPORTER或OTEL_METRICS_EXPORTER——默认配置已满足需求OTEL_LOGS_EXPORTER - 切勿在同一JVM中同时运行传统Elastic APM Agent与EDOT Agent
Examples
示例
See the EDOT Java setup guide for complete
Dockerfile and docker-compose examples.
完整的Dockerfile与docker-compose示例请参考EDOT Java 设置指南