docs: clarify that OTLP endpoint is not the APM Server URL#997
docs: clarify that OTLP endpoint is not the APM Server URL#997strawgate wants to merge 1 commit intoelastic:mainfrom
Conversation
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🔍 Preview links for changed docs |
- Replace `my-deployment.apm.…` with `my-deployment.ingest.…` in the setup example to avoid implying the APM Server URL should be used. - Change `server_url` mapping from "corresponds to" to "is replaced by" and link to the setup page for endpoint configuration details. Made-with: Cursor
strawgate
force-pushed
the
docs/clarify-otlp-endpoint-config
branch
from
5bbe78f to
bb974b9
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis pull request updates documentation for Elastic's OpenTelemetry Java agent's OTLP endpoint configuration. The migration guide clarifies that the Elastic server_url is "replaced by" the OpenTelemetry OTLP endpoint and adds a reference to the Setup section for configuration details. The Setup documentation example is corrected to use the Ingest endpoint URL instead of the APM endpoint URL for Elasticsearch. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
1 participant
Summary
my-deployment.apm.…withmy-deployment.ingest.…to match the actual OTLP ingest endpoint pattern (consistent with other EDOT SDK docs like PHP).server_urlmapping wording from "corresponds to" to "is replaced by" and add a link to the setup page for endpoint details.