Conversation
Introduces a new category for Chain Events (ETR Webhook) in the sidebar, including links to various how-to guides related to chain events, such as overview, quick start, configuration, and more.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Changed code block syntax from plain to text for better clarity in the quick start and webhook payload documentation sections.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Changed code block syntax from plain to text for improved clarity in the rate limits section.
…chain-listening docs: add Chain Events category to sidebar
…uide Introduced a new section detailing optional environment variables for OpenTelemetry configuration, enhancing clarity and usability for users.
…ation Removed the `OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION` entry to streamline the OpenTelemetry configuration guide and eliminate potential confusion for users.
…ration Reintroduced the `OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION` variable in the optional variables section to provide clear guidance on its usage for Prometheus-compatible histograms.
Included a warning in the scaling documentation to emphasize the necessity of a database when running multiple replicas to prevent duplicate events. Explained how the database facilitates lease management and progress persistence for replicas.
Replaced instances of the GitHub Container Registry image with the Docker Hub image for consistency across the quick start, registry API, and scaling documentation. This change simplifies the instructions for users by standardizing the image source.
…entation Changed the note regarding database requirements to a warning to better emphasize the necessity of configuring `DB_HOST` for registry management endpoints. This update enhances clarity for users regarding the implications of not having a connected database.
…l-documentation docs: add optional variables section to OpenTelemetry configuration g…
Feat/sync develop
|
Warning Review limit reached
More reviews will be available in 51 minutes and 24 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (12)
✨ 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 |
3 participants
No description provided.