docs: update package doc to reflect OTEL as primary tracing backend#19
docs: update package doc to reflect OTEL as primary tracing backend#19
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 7 minutes and 22 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the package-level documentation for tracing to describe OpenTelemetry/OTLP as the primary trace export path, aligning docs with the planned Jaeger client removal effort.
Changes:
- Update
doc.gopackage comment to reference OpenTelemetry + OTLP-compatible backends instead of direct Jaeger/Zipkin backends.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
23e8a4a to
f959e75
Compare
Summary
Update package doc comment to reflect that tracing is now via OpenTelemetry OTLP (supporting Jaeger, Grafana Tempo, Honeycomb, etc.) rather than listing Jaeger/Zipkin as direct backends.
Part of Jaeger client removal (go-coldbrew/core#50).