docs: update tracing docs for Jaeger client removal#43
Conversation
- Index.md: clarify OTEL as primary, Jaeger as OTLP backend - Packages.md: update tracing description - howto/Tracing.md: remove Jaeger as direct backend, clarify OTLP - integrations.md: rename Jaeger section to OTLP-compatible backends - config-reference.md: clarify Jaeger example uses OTLP Part of Jaeger client removal (go-coldbrew/core#50).
|
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 5 minutes and 54 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. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ 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 ColdBrew documentation to reflect removal of the Jaeger client from core and clarify that tracing is now done via OpenTelemetry OTLP (with Jaeger positioned as an OTLP-compatible backend).
Changes:
- Reframes Jaeger as an OTLP-compatible backend and updates tracing descriptions accordingly.
- Updates tracing how-to overview/examples to remove Jaeger as a direct backend option.
- Clarifies the Jaeger local-dev configuration example as “via OTLP”.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
Index.md |
Updates homepage feature blurb to emphasize OTLP-compatible backends (including Jaeger). |
Packages.md |
Updates package-level tracing description to OTLP-compatible backends via OpenTelemetry. |
howto/Tracing.md |
Removes Jaeger from page description and reframes tracing as OpenTelemetry OTLP + New Relic. |
integrations.md |
Renames/rewrites Jaeger section to position it among OTLP-compatible backends. |
config-reference.md |
Clarifies the Jaeger local development example is via OTLP. |
Comments suppressed due to low confidence (1)
integrations.md:199
- The section title now suggests this covers any OTLP-compatible backend, but the configuration text/example is still framed specifically around Jaeger ("To send traces to Jaeger…" / "Jaeger collector"). Consider either keeping the heading scoped to Jaeger (e.g., "Jaeger (via OTLP)") or updating the config text to be backend-agnostic and optionally adding brief notes/examples for other backends mentioned (Tempo/Honeycomb).
## Jaeger / OTLP-compatible backends
[Jaeger] is an open-source distributed tracing system. ColdBrew supports Jaeger (and any OTLP-compatible backend like Grafana Tempo, Honeycomb, etc.) through the OpenTelemetry OTLP exporter.
### Configuring
To send traces to Jaeger, configure the OTLP endpoint to point to your Jaeger collector:
```go
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Update docs to reflect that the Jaeger client library has been removed from ColdBrew core. Tracing is now exclusively via OpenTelemetry OTLP.
Part of go-coldbrew/core#50.