Skip to content

docs: add optional variables section to OpenTelemetry configuration g…#15

Merged
RishabhS7 merged 6 commits into
developfrom
TT-1360/fix-opentelemetry-optional-documentation
Jun 3, 2026
Merged

docs: add optional variables section to OpenTelemetry configuration g…#15
RishabhS7 merged 6 commits into
developfrom
TT-1360/fix-opentelemetry-optional-documentation

Conversation

@manishdex25
Copy link
Copy Markdown
Contributor

@manishdex25 manishdex25 commented Jun 1, 2026

…uide

Introduced a new section detailing optional environment variables for OpenTelemetry configuration, enhancing clarity and usability for users.

Summary by CodeRabbit

  • Documentation
    • Fixed OpenTelemetry how-to guide formatting to ensure the optional variables section displays correctly.

…uide

Introduced a new section detailing optional environment variables for OpenTelemetry configuration, enhancing clarity and usability for users.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 1, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8ff106d2-3804-439c-8083-71c0ea385003

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch TT-1360/fix-opentelemetry-optional-documentation

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 and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/how-tos/chain-events/opentelemetry.md`:
- Line 24: The document currently lists
OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION in the main required
configuration block and also in the Optional Variables table, causing confusion;
remove OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION from the main
configuration snippet (the line showing
OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION=explicit_bucket_histogram)
so it only appears in the Optional Variables section, and update any surrounding
text to indicate that only the first three variables are required while
OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION remains optional.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 28f7c079-022f-4db3-b0de-1dbe7dd9d156

📥 Commits

Reviewing files that changed from the base of the PR and between b964147 and e7195a4.

📒 Files selected for processing (1)
  • docs/how-tos/chain-events/opentelemetry.md

Comment thread docs/how-tos/chain-events/opentelemetry.md Outdated
…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.
@manishdex25 manishdex25 requested a review from RishabhS7 June 2, 2026 09:20
@manishdex25 manishdex25 self-assigned this Jun 2, 2026
…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.
@RishabhS7 RishabhS7 merged commit 641f3c1 into develop Jun 3, 2026
2 checks passed
@RishabhS7 RishabhS7 deleted the TT-1360/fix-opentelemetry-optional-documentation branch June 3, 2026 09:53
@coderabbitai coderabbitai Bot mentioned this pull request Jun 4, 2026
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