-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Rework and consolidate OTLP configuration related pages #17169
Conversation
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. |
…eral Triaging section to OTLP Troubleshooting
...tions/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp.mdx
Outdated
Show resolved
Hide resolved
...e-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp-troubleshooting.mdx
Outdated
Show resolved
Hide resolved
...e-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp-troubleshooting.mdx
Outdated
Show resolved
Hide resolved
...e-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp-troubleshooting.mdx
Outdated
Show resolved
Hide resolved
...e-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp-troubleshooting.mdx
Outdated
Show resolved
Hide resolved
...tions/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp.mdx
Outdated
Show resolved
Hide resolved
...tions/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp.mdx
Show resolved
Hide resolved
...tions/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp.mdx
Outdated
Show resolved
Hide resolved
|
||
* If you haven't already done so, sign up for a free [New Relic account](https://newrelic.com/signup). | ||
* Get the [license key](https://one.newrelic.com/launcher/api-keys-ui.launcher) for the New Relic account to which you want to report data. This license key will be used to [configure the `api-key` header](#api-key). | ||
* Review your OTLP version: New Relic uses [OTLP release v0.18.0](https://github.com/open-telemetry/opentelemetry-proto/releases/tag/v0.18.0). Later versions are supported but new features are not yet implemented. Experimental features which were are no longer available in 0.18.0 are not 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.
Hey I noticed this change just now. This is the type of info that users should be able to find, but doesn't need to be top of page. It won't matter to almost all users, and I think putting it up here prominently might bring unnecessary FUD.
OpenTelemetry -> Export OpenTelemetry to New Relic -> Attribute length
OpenTelemetry -> Export OpenTelemetry to New Relic -> Batching
OpenTelemetry -> Export OpenTelemetry to New Relic -> Compression
OpenTelemetry -> Export OpenTelemetry to New Relic -> OTLP versions
OpenTelemetry -> Get started -> Set up your own app
OpenTelemetry -> Export OpenTelemetry to New Relic
toOpenTelemetry -> Export with OTLP
OTLP Configuration
Data Mapping
child renamed toOTLP Data Mapping
to make the content more clearopentelemetry-best-practices-overview.mdx
document, which seems to be a remnant from the recent refactor