Skip to content

docs(observability): cite the right RFC-0001 node for the Grafana datasource - #198

Merged
vovinacci merged 1 commit into
mainfrom
fix/datasource-comment-rfc-letter
Jul 27, 2026
Merged

docs(observability): cite the right RFC-0001 node for the Grafana datasource#198
vovinacci merged 1 commit into
mainfrom
fix/datasource-comment-rfc-letter

Conversation

@vovinacci

Copy link
Copy Markdown
Owner

The comment above the Analytics Postgres datasource quoted RFC-0001's D5 edge as "grafana -->|historical dashboards| pgA". The RFC draws it to pgB (0001-polyglot-platform.md:98). pgA is the backend's db; Grafana never connects there, so the citation sent a reader to the wrong database while the config four lines below correctly targets postgres-analytics.

…asource

The comment above the Analytics Postgres datasource quoted RFC-0001's D5
edge as "grafana -->|historical dashboards| pgA". The RFC draws it to pgB
(0001-polyglot-platform.md:98). pgA is the backend's `db`; Grafana never
connects there, so the citation sent a reader to the wrong database while
the config four lines below correctly targets postgres-analytics.
@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 56 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 Plus

Run ID: 02e797c7-0c1d-48d7-b2ef-a5b5b8fe39d6

📥 Commits

Reviewing files that changed from the base of the PR and between 37257ce and 1e4dae1.

📒 Files selected for processing (1)
  • observability/grafana/provisioning/datasources/datasource.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/datasource-comment-rfc-letter

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

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

@vovinacci
vovinacci merged commit 87b0ce1 into main Jul 27, 2026
5 checks passed
@vovinacci
vovinacci deleted the fix/datasource-comment-rfc-letter branch July 27, 2026 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants