-
Notifications
You must be signed in to change notification settings - Fork 1.4k
(feat): K8S Otel GA Docs #20980
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
base: develop
Are you sure you want to change the base?
(feat): K8S Otel GA Docs #20980
Conversation
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Hi @WriteMayur 👋 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). |
## Enable Low Data Mode [#low-data] | ||
|
||
|
||
The `LowDataMode` option is enabled by default to ingest only the metrics required by our Kubernetes UIs. This mode reduces the amount of data collected, focusing on essential metrics for Kubernetes monitoring. To fetch additional metrics, you can add new pipelines and configuring the appropriate receivers and processors in your [`values.yaml`]() file using the `extraConfig` section. |
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.
IMHO We need to create a sub section in two
How to add metrics in top of LowDataMode should be a subsection with a subtitle
You must also add the `otlphttp/secondAccount` exporter to the relevant `pipelines` (metrics, traces, logs) within your `extraConfig` for both the `daemonset` and `deployment` collectors to ensure data is actually sent through this new exporter. | ||
</Callout> | ||
|
||
3. After updating your `values.yaml` file, apply the changes to your cluster: |
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.
Do we need to mention that the changes in the values file need to be applied?
Isn't it assumed?
If you think so, then we should add this step to the other sections in the doc too
This PR is to add the documentation support for New Relic OpenTelemetry for Kubernetes. It contains all the necessary information that customer might needs to install, and configure their K8S for New Relic and view the data in the New Relic.