-
Notifications
You must be signed in to change notification settings - Fork 3.1k
[pkg/datadog] add IgnoreMissingDatadogFields config flag for consumpt… #40226
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
[pkg/datadog] add IgnoreMissingDatadogFields config flag for consumpt… #40226
Conversation
…ion by datadog-agent connector
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.
In opentelemetry-collector-contrib, for now, using this flag will throw an error.
I think this warrants a changelog
This already throwed an error before (just the generic "unknown key" error). I don't think the error message changing warrants a changelog |
|
The error message is different than before, but I think that's fine if this is not intended to be used in -contrib. |
open-telemetry#40226) …ion by datadog-agent connector <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description IgnoreMissingDatadogFields is needed in datadog-agent fork of datadogconnector. In `opentelemetry-collector-contrib`, for now, using this flag will throw an error. In an upcoming datadog-agent PR, we will use this flag to control datadogconnector logic in datadog-agent's `stats.OTLPTracesToConcentratorInputsWithObfuscation`. Once that is merged, a follow up PR in `opentelemetry-collector-contrib` will bump the datadog-agent version and enable these changes, at which point we'll allow IgnoreMissingDatadogFields to be set. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
open-telemetry#40226) …ion by datadog-agent connector <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description IgnoreMissingDatadogFields is needed in datadog-agent fork of datadogconnector. In `opentelemetry-collector-contrib`, for now, using this flag will throw an error. In an upcoming datadog-agent PR, we will use this flag to control datadogconnector logic in datadog-agent's `stats.OTLPTracesToConcentratorInputsWithObfuscation`. Once that is merged, a follow up PR in `opentelemetry-collector-contrib` will bump the datadog-agent version and enable these changes, at which point we'll allow IgnoreMissingDatadogFields to be set. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
…ion by datadog-agent connector
Description
IgnoreMissingDatadogFields is needed in datadog-agent fork of datadogconnector. In
opentelemetry-collector-contrib, for now, using this flag will throw an error. In an upcoming datadog-agent PR, we will use this flag to control datadogconnector logic in datadog-agent'sstats.OTLPTracesToConcentratorInputsWithObfuscation. Once that is merged, a follow up PR inopentelemetry-collector-contribwill bump the datadog-agent version and enable these changes, at which point we'll allow IgnoreMissingDatadogFields to be set.Link to tracking issue
Fixes
Testing
Documentation