Fix run replication telemetry by passing in a tracer

[ericallam]

Summary by CodeRabbit

• New Features
  • Exposed additional tracing provider functionality for enhanced observability.
• Chores
  • Improved organization of import statements for better maintainability.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d11c5c7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The changes update the tracer utility by exposing the underlying tracer provider through the singleton export and enhancing the getTracer function to return the provider. The runs replication service is updated to accept a tracer provider, which is retrieved using the enhanced tracer utility.

Changes

File(s)	Change Summary
apps/webapp/app/v3/tracer.server.ts	Updated export to include provider alongside tracer and logger. Modified getTracer to return the provider object in all branches.
apps/webapp/app/services/runsReplicationInstance.server.ts	Reordered imports, added import for provider, and updated service initialization to include a tracer from the provider.

Poem

In the warren where tracers gleam,
Provider hops into the stream.
Services now can trace with glee,
Thanks to tweaks in code you see.
With every hop, a path anew—
The rabbits trace right next to you! 🐇✨

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 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 a815633 and d11c5c7.

📒 Files selected for processing (2)

• apps/webapp/app/services/runsReplicationInstance.server.ts (2 hunks)
• apps/webapp/app/v3/tracer.server.ts (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (7)

• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
• GitHub Check: units / 🧪 Unit Tests
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (5)

apps/webapp/app/v3/tracer.server.ts (3)

86-86: LGTM: Good addition of provider to the exported singleton

The change appropriately exposes the tracer provider through the singleton export, which allows other services to create specific named tracers.

---

158-159: LGTM: Maintains consistent interface in disabled mode

Good implementation - even when tracing is disabled, you're returning a NodeTracerProvider instance to maintain a consistent interface.

---

264-265: LGTM: Properly exposing the provider in the return object

Exposing the provider in the return object is a clean approach that allows services to create context-specific tracers.

apps/webapp/app/services/runsReplicationInstance.server.ts (2)

4-7: LGTM: Well-organized imports

Good reorganization of imports and addition of the provider import from the tracer server.

---

52-53: LGTM: Good integration with the tracer system

The addition of a service-specific tracer using provider.getTracer("runs-replication-service") is a clean approach to enable proper telemetry for the runs replication service.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.