Distributed Outbox And Transport Depth Telemetry

[patrickleet]

Summary

• Added bounded outbox claim, publish, message-age, retry-bucket, and extended backlog/runtime metrics.
• Added transport receive/in-flight duration metrics plus optional adapter-supplied age, delivery attempt, and lag hooks.
• Added outbox claim spans and enriched outbox publish / transport receive spans with bounded attributes.
• Updated metrics, observability, and transport docs.

Acceptance Criteria Addressed

• Existing metric family names and label meanings are preserved.
• New outbox and transport metric families render through Prometheus text exposition.
• Adapter-supplied delivery attempt, timestamp, and lag default to absent.
• Metric labels stay bounded and are covered by privacy tests.
• Dispatcher, publish-hook, in-memory store, SQLite SQL store, runner, metrics exposition, and OTel span tests cover the new paths.

Validation

• cargo check --all-targets --features "metrics http otel sqlite"
• cargo check --all-targets --features "http otel"
• cargo check --all-targets --features sqlite
• cargo test --features "metrics http otel sqlite"
• git diff --check

Notes

• tests/metrics_exposition ran in the full suite; promtool check metrics was skipped because PROMTOOL is not installed/set locally.

[coderabbitai]

Warning

Review limit reached

@patrickleet, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ce6dc104-d4eb-4a22-abcd-3c4e6bfc5a72

📥 Commits

Reviewing files that changed from the base of the PR and between 84a72f1 and 1b88a2e.

📒 Files selected for processing (23)

• docs/metrics.md
• docs/observability.md
• docs/transports.md
• src/bus/kafka.rs
• src/bus/postgres_bus.rs
• src/bus/runner.rs
• src/bus/source.rs
• src/bus/sql_bus_common.rs
• src/bus/sqlite_bus.rs
• src/lib.rs
• src/metrics.rs
• src/outbox_worker/mod.rs
• src/outbox_worker/outbox_dispatch.rs
• src/outbox_worker/outbox_source.rs
• src/outbox_worker/publish_hook.rs
• src/outbox_worker/store.rs
• src/postgres_repo/mod.rs
• src/sqlite_repo/mod.rs
• src/sqlx_repo/repo.rs
• src/telemetry.rs
• tests/metrics_exposition/main.rs
• tests/otel_export/main.rs
• tests/sqlite_repository/main.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch tasks--distributed-outbox-transport-depth-telemetry-1

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}