-
Notifications
You must be signed in to change notification settings - Fork 175
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
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
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. |
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
** Traces | ||
** Dependencies | ||
|
||
// screenshots here? |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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? |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
@raultorrecilla @vigneshshanmugam can we get someone from the team to review and fill in the gaps? |
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
+ | ||
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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: Miguel Luna <39376769+mlunadia@users.noreply.github.com>
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
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? |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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/
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc
Outdated
Show resolved
Hide resolved
// * https://elastic.github.io/opentelemetry/quickstart/serverless/docker.html[Docker Quickstart] | ||
|
||
[discrete] | ||
== Get creative with Discover |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
@elastic/obs-docs Could we please get some expert eyes on this? |
I'll merge this. Would still be good to get:
|
* 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
* 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
* 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
### Summary Ports elastic/observability-docs#4854 to V3. --------- Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
|
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