datafusion-comet
datafusion-comet copied to clipboard
[wip] feat: Add framework for supporting multiple telemetry providers
Which issue does this PR close?
Part of https://github.com/apache/datafusion-comet/issues/1718
Rationale for this change
Experimenting with supporting OpenTelemetry as an option.
What changes are included in this PR?
How are these changes tested?
With otel enabled, I see these warning in the executor logs:
25/05/08 11:42:59 WARN GrpcExporter: Failed to export spans. Server responded with gRPC status code 2. Error message: Failed to connect to localhost/127.0.0.1:4317
25/05/08 11:43:01 WARN GrpcExporter: Failed to export metrics. Server responded with gRPC status code 2. Error message: Failed to connect to localhost/127.0.0.1:4317
Codecov Report
Attention: Patch coverage is 50.00000% with 35 lines in your changes missing coverage. Please review.
Project coverage is 58.64%. Comparing base (
f09f8af) to head (c53c433). Report is 183 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #1722 +/- ##
============================================
+ Coverage 56.12% 58.64% +2.51%
- Complexity 976 1147 +171
============================================
Files 119 133 +14
Lines 11743 12696 +953
Branches 2251 2369 +118
============================================
+ Hits 6591 7445 +854
- Misses 4012 4072 +60
- Partials 1140 1179 +39
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
Current status:
Chrome
OpenTelemetry
I can see data in Jaegar, but I need to propagate the span in order to see nested events.