Skip to content

Commit 83c71a8

Browse files
authored
Apply suggestions from review
1 parent 3331efb commit 83c71a8

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

manage-data/data-store/data-streams/tsds-ingest-otlp.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,17 @@ In addition to the ingestion of metrics data through the bulk API,
1515

1616
The endpoint is available under `/_otlp/v1/metrics`.
1717

18+
## Overview and deployment options [best-practices]
19+
20+
:::{important}
21+
The recommended approach for sending OpenTelemetry Protocol (OTLP) data depends on your deployment:
22+
23+
- **{{ecloud}}:** Use the [Elastic Cloud Managed OTLP Endpoint](opentelemetry:/reference/motlp.md) directly.
24+
- **Self-managed:** Use the {{es}} OTLP endpoint described on this page, ideally through an OpenTelemetry Collector in [Gateway mode](elastic-agent://reference/edot-collector/config/default-config-standalone.md#gateway-mode).
25+
26+
For details on the recommended way to set up OpenTelemetry-based data ingestion, refer to the [EDOT reference architecture](opentelemetry:/reference/architecture/index.md).
27+
:::
28+
1829
Ingesting metrics data using the OTLP endpoint has the following advantages:
1930

2031
* Improved ingestion performance, especially if the data contains many resource attributes.

0 commit comments

Comments
 (0)