You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn how to use the Elastic Cloud Managed OTLP Endpoint to send logs, metrics, and traces to Elastic Observability.
2
+
description: Learn how to use the Elastic Cloud Managed OTLP Endpoint to send logs, metrics, and traces to Elastic Serverless and Elastic Cloud Hosted.
# Quickstart: Send OTLP data to Elastic Serverless or Elastic Cloud Hosted
10
13
11
-
The {{motlp}} is a fully managed offering exclusively for Elastic Cloud users that simplifies OpenTelemetry data ingestion. It provides an endpoint for OpenTelemetry SDKs and Collectors to send telemetry data, with Elastic handling scaling, data processing, and storage. Refer to [{{motlp}}](opentelemetry://reference/motlp.md) for more information.
14
+
You can send OpenTelemetry data to Elastic Serverless and Elastic Cloud Hosted using the {{motlp}} endpoint.
12
15
13
-
This endpoint is designed for the following use cases:
16
+
The {{motlp}} provides an endpoint for OpenTelemetry SDKs and Collectors to send telemetry data, with Elastic handling scaling, data processing, and storage. Refer to [{{motlp}}](opentelemetry://reference/motlp.md) for more information.
17
+
18
+
The {{motlp}} is designed for the following use cases:
14
19
15
20
* Logs & Infrastructure Monitoring: Logs forwarded in OTLP format and host and Kubernetes metrics in OTLP format.
16
21
* APM: Application telemetry in OTLP format.
17
22
18
-
In this quickstart guide, you'll learn how to use the {{motlp}} to send logs, metrics, and traces to Elastic.
19
-
20
-
## Prerequisites
21
-
22
-
* An {{obs-serverless}} project. To learn more, refer to [create an Observability project](/solutions/observability/get-started.md).
23
-
* A system forwarding logs, metrics, or traces in OTLP (any EDOT Collector or SDK—EDOT or community).
23
+
Keep reading to learn how to use the {{motlp}} to send logs, metrics, and traces to your Serverless project or {{ech}} cluster.
24
24
25
-
## Get started
25
+
:::{note}
26
+
:applies_to: { ess:, stack: preview 9.2 }
27
+
The Managed OTLP endpoint might not be available in all {{ech}} regions during the Technical Preview.
28
+
:::
26
29
27
30
## Send data to Elastic
28
31
29
32
Follow these steps to send data to Elastic using the {{motlp}}.
30
33
31
34
::::::{stepper}
32
35
33
-
:::::{step} Check the requirements
34
-
35
-
To use the {{motlp}} you need the following:
36
-
37
-
* An Elastic Observability Serverless project. Security projects are not yet supported.
38
-
* An OTLP-compliant shipper capable of forwarding logs, metrics, or traces in OTLP format. This can include the OpenTelemetry Collector (EDOT, Contrib, or other distributions), OpenTelemetry SDKs (EDOT, upstream, or other distributions), or any other forwarder that supports the OTLP protocol.
36
+
:::::{step} Retrieve your endpoint and API key
39
37
40
-
:::::
41
-
42
-
:::::{step} Locate your {{motlp}}
43
-
44
-
To retrieve your {{motlp}} endpoint address and an API key, follow these steps:
38
+
To retrieve your {{motlp}} endpoint address and API key, follow these steps:
45
39
40
+
::::{applies-switch}
41
+
:::{applies-item} serverless:
46
42
1. In {{ecloud}}, create an Observability project or open an existing one.
47
-
2. Select your project's name and then select **Manage project**.
48
-
3. Locate the **Connection alias** and select **Edit**.
49
-
4. Copy the **Managed OTLP endpoint** URL.
50
-
51
-
% ## commented out until mOTLP on ECH is available
52
-
% ### Elastic Cloud on Elasticsearch ({{ech}})
53
-
% 1. Open your deployment in the Elastic Cloud console.
54
-
% 2. Navigate to **Integrations** and find **OpenTelemetry** or **Managed OTLP**.
55
-
% 3. Copy the endpoint URL shown.
56
-
% ## Self-Managed
57
-
% For self-managed environments, you can deploy and expose an OTLP-compatible endpoint using the EDOT Collector as a gateway. Refer to [EDOT deployment docs](https://www.elastic.co/docs/reference/opentelemetry/edot-collector/modes#edot-collector-as-gateway).
58
-
%
59
-
% :::{note}
60
-
% Please reach out to support, and then Engineering can look into increasing it based on the license tier or for experimentation purposes.
61
-
% :::
62
-
63
-
:::::
64
-
65
-
:::::{step} Create an API key
43
+
2. Go to **Add data**, select **Applications** and then select **OpenTelemetry**.
44
+
3. Copy the endpoint and authentication headers values.
66
45
67
-
Generate an API key with appropriate ingest privileges to authenticate OTLP traffic:
68
-
69
-
1. In {{ecloud}}, go to **Manage project** → **API Keys**.
70
-
2. Select **Create API Key**.
71
-
3. Name the key. For example, `otlp-client`.
72
-
4. Edit the optional security settings.
73
-
5. Select **Create API Key**.
74
-
6. Copy the key to the clipboard.
75
-
76
-
Add this key to your final API key string. For example:
46
+
Alternatively, you can retrieve the endpoint from the **Manage project** page and create an API key manually from the **API keys** page.
47
+
:::
77
48
78
-
```
79
-
Authorization: ApiKey <your-api-key>
80
-
```
49
+
:::{applies-item} ess:
50
+
{applies_to}`stack: preview 9.2`
51
+
1. In {{ecloud}}, create an {{ech}} deployment or open an existing one.
52
+
2. Go to **Add data**, select **Applications** and then select **OpenTelemetry**.
53
+
3. Copy the endpoint and authentication headers values.
81
54
82
-
:::{important}
83
-
The API key copied from Kibana does not include the `ApiKey` scheme. Always prepend `ApiKey ` before using it in your configuration or encoding it for Kubernetes secrets. For example:
84
-
85
-
- Correct: `Authorization: ApiKey abc123`
86
-
- Incorrect: `Authorization: abc123`
55
+
Alternatively, you can retrieve the endpoint from the **Manage project** page and create an API key manually from the **API keys** page.
87
56
:::
57
+
::::
88
58
89
59
:::::
90
60
91
-
:::::{step} Send data to the {{motlp}}
61
+
:::::{step} Configure your OTLP shipper
92
62
93
-
The final step is to use the {{motlp}} endpoint and your Elastic API key to send data to {{ecloud}}.
63
+
The final step is to configure your Collector or SDK to use the {{motlp}} endpoint and your Elastic API key to send data to {{ecloud}}.
94
64
95
65
::::{tab-set}
96
66
@@ -100,27 +70,21 @@ To send data to the {{motlp}} from the {{edot}} Collector or the contrib Collect
100
70
```yaml
101
71
exporters:
102
72
otlp:
103
-
endpoint: https://<motlp-endpoint> <1>
73
+
endpoint: https://<motlp-endpoint>
104
74
headers:
105
-
Authorization: ApiKey <your-api-key> <2>
75
+
Authorization: ApiKey <your-api-key>
106
76
```
107
77
108
-
1. The endpoint retrieved at [step 2](#locate-your-motlp)
109
-
2. The API key created at [step 3](#create-an-api-key)
110
-
111
78
Set the API key as an environment variable or directly in the configuration as shown in the example.
112
79
:::
113
80
114
81
:::{tab-item} OpenTelemetry SDK example
115
82
To send data to the {{motlp}} from {{edot}} SDKs or contrib SDKs, set the following variables in your application's environment:
1. The endpoint retrieved at [step 2](#locate-your-motlp)
123
-
2. The API key created at [step 3](#create-an-api-key)
124
88
:::
125
89
126
90
:::{tab-item} Kubernetes example
@@ -141,14 +105,11 @@ Mount the secret as an environment variable or file, then reference it in your O
141
105
```yaml
142
106
exporters:
143
107
otlp:
144
-
endpoint: https://<motlp-endpoint> <1>
108
+
endpoint: https://<motlp-endpoint>
145
109
headers:
146
-
Authorization: ${API_KEY} <2>
110
+
Authorization: ${API_KEY}
147
111
```
148
112
149
-
1. The endpoint retrieved at [step 2](#locate-your-motlp)
150
-
2. The API key created at [step 3](#create-an-api-key)
151
-
152
113
And in your deployment spec:
153
114
154
115
```yaml
@@ -173,15 +134,15 @@ When creating a Kubernetes secret, always encode the full string in Base64, incl
173
134
174
135
## Differences from the Elastic APM Endpoint
175
136
176
-
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/opentelemetry/index.md), which primarily focuses on traces and the APM use case.
137
+
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.
177
138
178
-
## Troubleshoot
139
+
## Troubleshooting
179
140
180
141
The following sections provide troubleshooting information for the {{motlp}}.
181
142
182
-
### I don't have a Collector or SDK running
143
+
### You don't have a Collector or SDK running
183
144
184
-
Don't have a collector or SDK running? Spin up an EDOT collector in just a few steps:
145
+
Don't have a collector or SDK running? Spin up an EDOT collector in few steps:
@@ -201,14 +162,14 @@ You must format your API key as `"Authorization": "ApiKey <api-key-value-here>"`
201
162
202
163
### Error: too many requests
203
164
204
-
The Managed OTLP endpoint has per-project rate limits in place. If you hit this limit, reach out to our [support team](https://support.elastic.co). Refer to [Rate limiting](opentelemetry://reference/motlp.md#rate-limiting) for more information.
165
+
The Managed OTLP endpoint has per-project rate limits in place. If you reach this limit, reach out to our [support team](https://support.elastic.co). Refer to [Rate limiting](opentelemetry://reference/motlp.md#rate-limiting) for more information.
205
166
206
167
## Provide feedback
207
168
208
169
Help improve the Elastic Cloud Managed OTLP Endpoint by sending us feedback in our [discussion forum](https://discuss.elastic.co/c/apm) or [community Slack](https://elasticstack.slack.com/signup#/domain-signup).
209
170
210
171
For EDOT collector feedback, open an issue in the [elastic-agent repository](https://github.com/elastic/elastic-agent/issues).
211
172
212
-
## What's next?
173
+
## What's next
213
174
214
175
Visualize your OpenTelemetry data. Learn more in [](/solutions/observability/otlp-visualize.md).
0 commit comments