-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
internal/splunk: fallback to host if cloud resource id not found #1170
Conversation
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.
splunk is the only vendor specific thing in common anymore, would you consider moving that to internal/splunk please?
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.
LGTM
I will do in followup PR. I should make internal/splunk its own go module I assume? |
Build failed. |
Please rebase |
APM correlation will need to do same thing so add fallback logic in common.
Codecov Report
@@ Coverage Diff @@
## master #1170 +/- ##
==========================================
- Coverage 89.82% 89.77% -0.05%
==========================================
Files 285 285
Lines 13882 13878 -4
==========================================
- Hits 12469 12459 -10
- Misses 1044 1052 +8
+ Partials 369 367 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@tigrannajaryan fixed |
Note: All of the cudos go to @dneray for the logic/testing/effort in open-telemetry/opentelemetry-collector#981 This pr is based off of it with the following modifications - The config looks like ``` - key : <key to use for applying the rule too> pattern: <the regex pattern with named submatchers> action: extract ``` I think that the original PR is going in the right way for what we can the internal logic to be but as the issue #979 and #1170 indicate we need to take a step back and redesign the attributes processor (or make it clear of its limitations). This pr unblocks the required functionality. **Link to tracking Issue:** #979 **Link to follow up issue:** #1170 **Testing:** Added tests for extracting. **Documentation:** Updated processor readme.
…#1170) * Don't consider unset env var an error during detection * update CHANGELOG
APM correlation will need to do same thing so add fallback logic in common.