Skip to content

Align EDOT docs wording for Managed OTLP targets and crash reporting support #620

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Copilot wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Align EDOT docs wording for Managed OTLP targets and crash reporting support #620

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e6f1d65
Initial plan
Copilot Jun 19, 2026
f57b986
docs: fix coherence wording
Copilot Jun 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/reference/compatibility/edot-vs-upstream.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ Due to current upstream limitations, some capabilities are temporarily available
| Inferred spans | Available in EDOT only. Generates spans from profiling data without manual instrumentation, closing visibility gaps that auto-instrumentation does not cover. |
| Central configuration | Available in EDOT only. Manages SDK settings from {{kib}} through the EDOT Collector using [OpAMP](/reference/central-configuration.md). Most SDKs apply configuration changes dynamically, without restarting or redeploying applications. |
| Profiling integration | Available in EDOT Java only. Correlates traces with continuous profiling data for deeper performance analysis. |
| Crash reporting | Available in EDOT only. Captures native crash data on mobile platforms for post-mortem analysis. |
| Crash reporting | Available in EDOT only. Captures native crash data on supported mobile platforms (currently iOS only) for post-mortem analysis. |

Upstream OTel SDKs are technically [Compatible] with Elastic and can send data through the same ingestion paths, but Elastic does not provide official support or troubleshooting assistance for them. Refer to the [SDK compatibility table](sdks.md) for version-level details.

Expand Down
3 changes: 1 addition & 2 deletions docs/reference/edot-cloud-forwarder/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ products:

The Elastic Distribution of OpenTelemetry (EDOT) Cloud Forwarder provides the EDOT Collector as a function to collect and send your telemetry data to Elastic Observability from AWS, GCP, and Azure. {{edot-cf}} can collect telemetry data from object storage and cloud services.

{{edot-cf}} sends the data it collects directly to the [Managed OTLP endpoint](docs-content://solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md) of {{serverless-full}}.
{{edot-cf}} sends the data it collects directly to the [Managed OTLP endpoint](docs-content://solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md) of {{ecloud}}.

## Supported cloud providers and services

Expand All @@ -36,4 +36,3 @@ To get started with {{edot-cf}}, select the setup guide for your cloud provider:
- [Azure](edot-cloud-forwarder-azure://reference/edot-cf-azure/index.md)
- [GCP](gcp/index.md)