Skip to content

Collect data with Elastic Cloud Native OpenTelemetry Endpoint #4854

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.

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

Merged
merged 6 commits into from
Apr 1, 2025

Conversation

bmorelli25
Copy link
Member

@bmorelli25 bmorelli25 commented Mar 21, 2025

Description

This is a very rough outline of a potential Getting Started with Elastic Cloud Native OpenTelemetry Endpoint Guide. After we come to a consensus on the final guide, I will port to Markdown and our new documentation system.

Important

Reviewers: I've left comments and questions in the Asciidoc files. Please take a look and leave feedback.

Issues, People, etc.

closes #4851

Copy link
Contributor

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

** Traces
** Dependencies

// screenshots here?
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe the APM workflow is the first one we should call out here? @mlunadia thoughts?

Copy link
Member Author

Choose a reason for hiding this comment

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

++ need some input on what to do with this section. Added a brief overview on our APM UI for now.

* Kubernetes
** (Optional) Install the OpenTelemetry Assets integrations to access the ‘[OTEL][Metrics Kubernetes] Cluster Overview’ dashboard.

// screenshots here?
Copy link
Contributor

Choose a reason for hiding this comment

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

We should show a screenshot of the k8S assets that are included in the new OTel compatible content pack.

Copy link
Member Author

Choose a reason for hiding this comment

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

Is there a cluster with relevant data that I can use to take this screenshot?

@mlunadia
Copy link

@raultorrecilla @vigneshshanmugam can we get someone from the team to review and fill in the gaps?

+
NOTE: Follow this flow for all use cases, including logs and infrastructure monitoring.

. Copy the `OTEL_EXPORTER_OTLP_ENDPOINT` URL. Replace `.apm` with `.ingest` and save this value for later.

Choose a reason for hiding this comment

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

Users will no longer have to edit the endpoint, the actual endpoint url will be displayed in the cloud console and also in the application onboarding. I recommend we guide users to obtain the endpoint from cloud console.

Choose a reason for hiding this comment

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

image

Copy link
Member Author

Choose a reason for hiding this comment

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

To clarify: We should recommend users go to the cloud console for both the Endpoint and API key, not the onboarding flow?

Should we doc both?

Copy link
Member Author

@bmorelli25 bmorelli25 Mar 25, 2025

Choose a reason for hiding this comment

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

Update to: "Managed OTLP endpoint"
Update to use Cloud Console to reduce confusion about what type of data is supported

Copy link
Member Author

Choose a reason for hiding this comment

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

@mlunadia I'm not able to replicate this page in the cloud console.

When I click on "Manage project API keys" I'm taken to this page
Screenshot 2025-03-26 at 8 03 06 PM

bmorelli25 and others added 2 commits March 24, 2025 15:40
Co-authored-by: Miguel Luna <39376769+mlunadia@users.noreply.github.com>
@bmorelli25 bmorelli25 marked this pull request as ready for review March 25, 2025 02:10
@bmorelli25 bmorelli25 requested a review from a team as a code owner March 25, 2025 02:10
In your {obs-serverless} project, go to **Integrations** and toggle **Display beta integrations**.
Search for "OpenTelemetry" and select and install **Kubernetes OpenTelemetry Assets**.

// Does anyone have a cluster with relevant data that we can use to take a screenshot of this dashboard?
Copy link
Member Author

Choose a reason for hiding this comment

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

Asked above too

Does anyone have a cluster with relevant data that we can use to take a screenshot of this dashboard?

Copy link
Member

Choose a reason for hiding this comment

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

@mlunadia ^^ could you provide it since you have already have one running. Thanks

* https://elastic.github.io/opentelemetry/quickstart/serverless/k8s.html[Kubernetes Quickstart]
* https://elastic.github.io/opentelemetry/quickstart/serverless/hosts_vms.html[Hosts & VMs Quickstart]

// Commenting out Docker until the docs are ready
Copy link
Member Author

@bmorelli25 bmorelli25 Mar 25, 2025

Choose a reason for hiding this comment

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

Other is focussed on on infra. This will focus on use case
APM coming soon here: https://elastic.github.io/opentelemetry/use-cases/application/

// * https://elastic.github.io/opentelemetry/quickstart/serverless/docker.html[Docker Quickstart]

[discrete]
== Get creative with Discover
Copy link
Member Author

Choose a reason for hiding this comment

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

Move this to a new page in apps and services

Make for ANY otlp data

Copy link
Member Author

Choose a reason for hiding this comment

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

End goal is analysis of OTLP data in one place

@jlind23
Copy link
Contributor

jlind23 commented Apr 1, 2025

@elastic/obs-docs Could we please get some expert eyes on this?

@bmorelli25
Copy link
Member Author

I'll merge this. Would still be good to get:

  • The screenshot mentioned above
  • Input on what to do with the APM section
  • Clarification on why I can't access the endpoint from the cloud console like @mlunadia suggests
  • Clarification on when the APM docs will be available

@bmorelli25 bmorelli25 merged commit ffa8978 into do-not-delete_legacy-docs Apr 1, 2025
5 checks passed
@bmorelli25 bmorelli25 deleted the motel-docs branch April 1, 2025 23:13
@bmorelli25 bmorelli25 added the backport-8.x Automated backport to the 8.x branch with mergify label Apr 1, 2025
@bmorelli25 bmorelli25 added backport-8.17 Automated backport with mergify backport-8.18 Automated backport to the 8.18 branch labels Apr 1, 2025
mergify bot pushed a commit that referenced this pull request Apr 1, 2025
* add very rough draft

* Apply suggestions from code review

Co-authored-by: Miguel Luna <39376769+mlunadia@users.noreply.github.com>

* address feedback

* fix bad link

* more updates

* clean up

---------

Co-authored-by: Miguel Luna <39376769+mlunadia@users.noreply.github.com>
(cherry picked from commit ffa8978)

# Conflicts:
#	docs/en/serverless/index.asciidoc
mergify bot pushed a commit that referenced this pull request Apr 1, 2025
* add very rough draft

* Apply suggestions from code review

Co-authored-by: Miguel Luna <39376769+mlunadia@users.noreply.github.com>

* address feedback

* fix bad link

* more updates

* clean up

---------

Co-authored-by: Miguel Luna <39376769+mlunadia@users.noreply.github.com>
(cherry picked from commit ffa8978)

# Conflicts:
#	docs/en/serverless/index.asciidoc
mergify bot pushed a commit that referenced this pull request Apr 1, 2025
* add very rough draft

* Apply suggestions from code review

Co-authored-by: Miguel Luna <39376769+mlunadia@users.noreply.github.com>

* address feedback

* fix bad link

* more updates

* clean up

---------

Co-authored-by: Miguel Luna <39376769+mlunadia@users.noreply.github.com>
(cherry picked from commit ffa8978)

# Conflicts:
#	docs/en/serverless/index.asciidoc
bmorelli25 added a commit to elastic/docs-content that referenced this pull request Apr 2, 2025
### Summary

Ports elastic/observability-docs#4854 to V3.

---------

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
@mlunadia
Copy link

mlunadia commented Apr 3, 2025

  • @bmorelli25 the endpoint is behind the edit connection alias, not a very intuitive UI unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify backport-8.17 Automated backport with mergify backport-8.18 Automated backport to the 8.18 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Request]: Document Public Tech Preview: Managed OTLP Endpoint for Serverless Users
4 participants