Move OpenTelemetry infrastructure monitoring examples to examples repository #17742
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @jack-berg 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
rhetoric101
previously approved these changes
Jun 24, 2024
rhetoric101
added
content
rhetoric101
approved these changes
Jun 24, 2024
There was a problem hiding this comment.
@jack-berg thanks for moving these examples outside the docs!
|
|
||
| ## Correlating infrastructure with OpenTelemetry APM [#infrastructure-correlation] | ||
|
|
||
| The following examples demonstrate using the collector to correlate [APM OpenTelemetry data](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-intro) with infrastructure. The general pattern is to configure the collector with a processor which detects and enriches the APM telemetry with additional environment context in the form of resource attributes, before exporting the data to New Relic via OTLP. New Relic can detect this correlation data and construct [relationships between APM and infrastructure entities](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-best-practices-resources). | ||
|
|
||
| - [Hosts](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-hosts) | ||
| - [Kubernetes](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-k8s) | ||
| * [Hosts](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-hosts) |
There was a problem hiding this comment.
@jack-berg this link is to one of the files that was removed. I am going to remove this link from the doc. If you need to add this back, you can do so later.
This was referenced Jun 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Combination of several PRs to move otel infrastructure monitoring examples to the examples repo. All the PRs touch the same set of files so merging sequentially will be tedious.