chore(deps): reduce observability dependency drift

[yordis]

• Stale observability dependencies delay exporter correctness and interoperability fixes.
• Keeping telemetry components aligned reduces incompatibility risk across tracing and metrics.
• Explicit scrape-contract coverage protects monitoring integrations as the exporter evolves.

[cursor]

PR Summary

Low Risk
Dependency-only bump plus a new metrics contract test; no production code changes in the diff, though telemetry exporter behavior may shift with OpenTelemetry 1.17.

Overview
Bumps centrally managed OpenTelemetry packages from 1.16.0 to 1.17.0 (including Prometheus.AspNetCore to 1.17.0-beta.1) and Microsoft.Extensions.Diagnostics.Testing from 10.7.0 to 10.8.0 in Directory.Packages.props.

Adds an integration test on /-/metrics that sends Accept: application/openmetrics-text; version=1.0.0 and asserts 200, application/openmetrics-text content type, and a body ending with # EOF\n, alongside the existing plain-text metrics test.

^{Reviewed by Cursor Bugbot for commit da474ed. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 51 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e85ecb83-ccd4-468d-aad9-a4a6f2f753a9

📥 Commits

Reviewing files that changed from the base of the PR and between ef70c57 and da474ed.

📒 Files selected for processing (2)

• src/Directory.Packages.props
• src/EventStore.Core.Tests/Services/Transport/Http/http_service_should.cs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch yordis/chore-refresh-observability-dependencies

---

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.}