docs(canary-checker): refresh check reference coverage#521
Conversation
Align the Canary Checker docs with the current checker registry before the next release. Add missing active check references for Dynatrace and OpenSearch, document removed legacy check fields, replace inline YAML examples with fixture imports where fixtures exist, and update cross-links from Mission Control. Update shared field components and the canary-checker submodule pointer so rendered reference tables and embedded source docs match the current API and runtime behavior.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
❌ Deploy Preview for canarychecker failed. Why did it fail? →
|
|
Warning Review limit reached
Next review available in: 56 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (50)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
1 participant
Canary Checker is preparing a new release, and the docs had drifted from the current checker registry.
This refresh aligns reference pages with active runtime checks, adds missing Dynatrace and OpenSearch docs, documents legacy fields that now route to removed checkers, and updates fixture-backed examples and Mission Control cross-links.
The shared field components now reflect current common check fields and connection behavior, and the canary-checker submodule points at the README accuracy update.