Skip to content

Commit 92da069

Browse files
committed
Reorg content
1 parent a559193 commit 92da069

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,6 @@ This endpoint is designed for the following use cases:
1717
* Logs & Infrastructure Monitoring: Logs forwarded in OTLP format and host and Kubernetes metrics in OTLP format.
1818
* APM: Application telemetry in OTLP format.
1919

20-
:::{dropdown} Differences from the existing Elastic APM Endpoint
21-
The Elastic Cloud Managed OTLP Endpoint ensures that OpenTelemetry data is stored without any schema translation, preserving both OpenTelemetry semantic conventions and resource attributes. It supports ingesting OTLP logs, metrics, and traces in a unified manner, ensuring consistent treatment across all telemetry data. This marks a significant improvement over the [existing functionality](/solutions/observability/apm/use-opentelemetry-with-apm.md), which primarily focuses on traces and the APM use case.
22-
:::
23-
2420
## Prerequisites
2521

2622
* An {{obs-serverless}} project. To learn more, refer to [create an Observability project](/solutions/observability/get-started.md).
@@ -43,7 +39,7 @@ To use the {{motlp}} you need the following:
4339

4440
:::::
4541

46-
:::::{step} Locate Your {{motlp}} Endpoint
42+
:::::{step} Locate your {{motlp}}
4743

4844
To retrieve your {{motlp}} endpoint address and an API key, follow these steps:
4945

@@ -172,6 +168,10 @@ When creating a Kubernetes secret, always encode the full string in Base64, incl
172168

173169
::::::
174170

171+
## Differences from the Elastic APM Endpoint
172+
173+
The Elastic Cloud Managed OTLP Endpoint ensures that OpenTelemetry data is stored without any schema translation, preserving both OpenTelemetry semantic conventions and resource attributes. It supports ingesting OTLP logs, metrics, and traces in a unified manner, ensuring consistent treatment across all telemetry data. This marks a significant improvement over the [existing functionality](/solutions/observability/apm/use-opentelemetry-with-apm.md), which primarily focuses on traces and the APM use case.
174+
175175
## Troubleshoot
176176

177177
### I don't have a Collector or SDK running

0 commit comments

Comments
 (0)