-
Notifications
You must be signed in to change notification settings - Fork 506
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
automatically add traces / metrics paths #806
automatically add traces / metrics paths #806
Conversation
noting that we could probably add logs exporter -- I noticed there was documentation for log signals, but the logs.rs exporter doesn't exist :) |
Ahh yeah once we merged #788 we can implement a logs exporter |
Codecov Report
@@ Coverage Diff @@
## main #806 +/- ##
=====================================
Coverage 69.7% 69.8%
=====================================
Files 110 110
Lines 9061 9072 +11
=====================================
+ Hits 6324 6334 +10
- Misses 2737 2738 +1
Continue to review full report at Codecov.
|
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.
I think it generally looks good. Thanks! The CI failure seems to be caused by unformatted code. Running cargo fmt
should fix it.
One ask I have is maybe we can add some document to explain the relationship between OTEL_EXPORTER_OTLP_END
and OTEL_EXPORTER_OTLP_{signal}_ENDPOINT
like https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#endpoint-urls-for-otlphttp.
And reference it from env var constants. It may be easier for user to understand what to choose
Co-authored-by: Zhongyang Wu <zhongyang.wu@outlook.com>
…ayfair-contribs/opentelemetry-rust into oltp_http_exporter_signal_path
added links to the spec from those constants -- hope that helps! |
I can make an issue or continue from #773 when it is merged! feel free to assign me or let me know here! |
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.
It seems log may need sometime to land. I think we can close #773 and create a new one for add log path and related envionment variables.
The change looks nice 👍
Just waiting on tests/lints now? |
sorry about that -- doesn't run without maintainers clicking it so the feedback loop is long :) |
It only applies to the first PR(to prevent bad actors from injecting crypto code in PR to exploit CI pipeline). Should be better once it's merged |
Running |
alright let me run that and be back in a sec |
Emm looks like the EasyCLA stuck again 😞 |
no worries. I'll find something to fix i'm sure with the script and push a new one up |
nice! looks like it went through 💯 Thanks for the help :) |
Resolves #773