-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Log Support in Attribute Processor (2/2) #1830
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1830 +/- ##
==========================================
- Coverage 91.36% 91.32% -0.05%
==========================================
Files 280 278 -2
Lines 16640 16535 -105
==========================================
- Hits 15203 15100 -103
+ Misses 1006 1003 -3
- Partials 431 432 +1
Continue to review full report at Codecov.
|
BTW, I was playing with it, checking if it can extract information from the standard log file name format in K8s:
And it worked out of the box:
|
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 - In addition to the comments/making code coverage happy, please update:
- https://github.com/open-telemetry/opentelemetry-collector/blob/master/processor/attributesprocessor/testdata/config.yaml to include examples for logs
- Update the readme to reflect it working on logs format too.
This complements the trace span support already present. It shares the same config struct to maintain backwards-compatibility with spans in the cleanest way possible.
ok @ccaraman copy/paste stuff should be fixed now. |
BTW, I think there's a room to generalise the code for testing logs/metrics/trace processors. One example in which I did it is here, though I guess there might be better ways to do it. Perhaps it should be extracted as a some sort of helper (just thinking out loud) |
just tried this out in #1934 - I think it looks readable without any helper methods - just using table tests. |
CLosing in favor of #1934. |
* Remove bundler from Jaeger exporter * Update dependencies * Add changes to changelog * Add PR number to changelog
This complements the trace span support already present.
It shares the same config struct to maintain backwards-compatibility with spans in the cleanest way possible.
Ignore the first commit, it is in PR #1783.