fix: typo in env var name

[rupesh1]

• ref: https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/#otel_exporter_otlp_endpoint

---

Important

Fix typo in openllmetry/configuration.mdx, changing OTLP_EXPORTER_OTLP_ENDPOINT to OTEL_EXPORTER_OTLP_ENDPOINT.

• Documentation:
  • Fix typo in openllmetry/configuration.mdx, changing OTLP_EXPORTER_OTLP_ENDPOINT to OTEL_EXPORTER_OTLP_ENDPOINT to align with OpenTelemetry standards.

^{This description was created by for 7257a6a. You can customize this summary. It will automatically update as commits are pushed.}

Summary by CodeRabbit

• Documentation
  • Corrected the environment variable name in the documentation to align with the standard OpenTelemetry naming convention.

[coderabbitai]

Walkthrough

The documentation was updated to correct the name of an environment variable, changing OTLP_EXPORTER_OTLP_ENDPOINT to OTEL_EXPORTER_OTLP_ENDPOINT to match the standard OpenTelemetry naming convention.

Changes

File(s)	Change Summary
openllmetry/configuration.mdx	Fixed environment variable name in documentation note.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A bunny hopped through docs today,
Fixing a name that went astray.
Now OTEL shines, so clear and bright,
With variables named just right.
Hippity-hop, the docs are neat—
OpenTelemetry can’t be beat! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a52ff55 and 7257a6a.

📒 Files selected for processing (1)

• openllmetry/configuration.mdx (1 hunks)

🔇 Additional comments (1)

openllmetry/configuration.mdx (1)

54-57: Verified: No lingering OTLP_EXPORTER_OTLP_ENDPOINT occurrences
The incorrect environment variable name has been fully removed from the repository and replaced with OTEL_EXPORTER_OTLP_ENDPOINT to match the OpenTelemetry spec. No further action required—LGTM.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 7257a6a in 35 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. openllmetry/configuration.mdx:56

• Draft comment:
  Fixes typo: correctly uses OTEL_EXPORTER_OTLP_ENDPOINT per OpenTelemetry standard.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it only states that a typo was fixed and the correct usage of a standard is applied. It does not provide a suggestion, ask for confirmation, or point out a potential issue.

Workflow ID: wflow_DsCQdglUWvUzVocf

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[nirga]

Thanks! @rupesh1