docs(opentelemetry): add additional configuration parameters for OpenTelemetry in Kubernetes #33268
Conversation
This file contains hidden or 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
…ogs in OTLP ingest configs
Contributor
|
Hi @jfmainville, thanks for your submission to the Datadog docs! We'll follow up soon to validate the proposed changes and proceed with applying them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this PR do? What is the motivation?
This PR contains adjustements to the OTLP configuration to include the metrics, traces and logs default configuration. There wasn't a clear indication in the Datadog documentation regarding the fact that the logs were disabled by default. Having these default values included in the default configuration will reduce the risk of encountering issues with the logs ingestion process.
Merge instructions
Merge readiness:
Additional notes