Skip to content

Conversation

@felixbarny
Copy link
Member

@felixbarny felixbarny commented Oct 7, 2025

Adds docs for the new OTLP endpoint added via elastic/elasticsearch#133057

Closes #3363

@felixbarny felixbarny self-assigned this Oct 7, 2025
@felixbarny felixbarny requested review from a team as code owners October 7, 2025 06:57
Copy link
Contributor

@theletterf theletterf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent work, Felix! Made some edits and left a couple of questions.

Copy link
Contributor

@theletterf theletterf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! We can merge when you're ready.

@felixbarny
Copy link
Member Author

I had a chat with Kostas and I've reworked the information architecture a bit. We want to promote OTEL-based ingestion as an easier way to get data into TSDB. At the same time, we want to de-emphasize the ES OTLP Endpoint as users shouldn't directly send data to it. The data should go to an OTel collector or the managed OTLP Endpoint on serverless. These can then use the ES OTLP Endpoint as and implementation detail.

@marciw
Copy link
Contributor

marciw commented Oct 7, 2025

LGTM! We can merge when you're ready.

These commits are in my branch -- so no, not ready to merge yet 🙃

@theletterf
Copy link
Contributor

@marciw Ah! I didn't notice that it's not targeting main. @felixbarny please defer to Marci's for when to merge these — thanks!

Copy link
Member

@vigneshshanmugam vigneshshanmugam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

If you're looking to ingest OpenTelemetry metrics,
follow the [OpenTelemetry quickstarts](/solutions/observability/get-started/opentelemetry/quickstart/index.md).
This allows you to start sending data into a TSDS without having to worry about manually setting up data streams or configuring mappings.
::::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One the fence about having it here as well.. will defer to @marciw

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO, linking from the TSDS quickstart to the OTel quickstart kinda makes sense.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ok with the addition, except it kind of takes over the top of the page. But I can maybe work on making it a bit smaller -- OK as is for now

::::{note}
If you're looking to ingest OpenTelemetry metrics,
follow the [OpenTelemetry quickstarts](/solutions/observability/get-started/opentelemetry/quickstart/index.md).
This allows you to start sending data into a TSDS without having to worry about manually setting up data streams or configuring mappings.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe: "For more details on how this is handled in Elasticsearch, check out [OTLP/HTTP endpoint
]{...}"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After this is merged into my branch, I'll make sure everything matches Elastic docs style (this note can be shorter and more direct)

Copy link
Contributor

@marciw marciw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I will make a few more edits in my in-progress PR after this is merged 👍

If you're looking to ingest OpenTelemetry metrics,
follow the [OpenTelemetry quickstarts](/solutions/observability/get-started/opentelemetry/quickstart/index.md).
This allows you to start sending data into a TSDS without having to worry about manually setting up data streams or configuring mappings.
::::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ok with the addition, except it kind of takes over the top of the page. But I can maybe work on making it a bit smaller -- OK as is for now

::::{note}
If you're looking to ingest OpenTelemetry metrics,
follow the [OpenTelemetry quickstarts](/solutions/observability/get-started/opentelemetry/quickstart/index.md).
This allows you to start sending data into a TSDS without having to worry about manually setting up data streams or configuring mappings.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After this is merged into my branch, I'll make sure everything matches Elastic docs style (this note can be shorter and more direct)

@marciw
Copy link
Contributor

marciw commented Oct 7, 2025

hmm, let's hold off on merging this until I can clarify how/whether @elastic/admin-docs additional dev-docs ppl should review -- stay tuned 🙏

Copy link
Contributor

@kilfoyle kilfoyle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚢
Very nice @felixbarny!

@felixbarny felixbarny merged commit 3fc8503 into elastic:mw-tsds-final-countdown Oct 8, 2025
6 checks passed
@felixbarny felixbarny deleted the otlp branch October 8, 2025 13:57
@marciw
Copy link
Contributor

marciw commented Oct 8, 2025

hmm, let's hold off on merging this until I can clarify how/whether @elastic/admin-docs additional dev-docs ppl should review -- stay tuned 🙏

@felixbarny ah sigh, didn't want you to merge this yet 😢

can you check with me first, if you're planning to work with my branch further? thank you!

@felixbarny
Copy link
Member Author

Ah, sorry, I thought the additional approval of @kilfoyle, who is part of admin-docs was what I was waiting for.

I'm not planning to make further changes to your branch. Feel free to revert if it's causing issues and we can re-do it later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants