chore: replaced Sentry with faro

[ApekshaBhosale]

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Bug Fixes
  • Improved error reporting for certain errors to provide more detailed information.

[coderabbitai]

Walkthrough

The change updates the error handling in the evalErrorHandler saga by replacing the use of Sentry.captureMessage with a call to captureException, passing the full error object and an explicit error name. This adjustment affects how errors of type UPDATE_DATA_TREE_ERROR are reported, providing more detailed information to the error tracking system. Local error logging remains unchanged, and no exported or public entity declarations are altered.

Changes

File(s)	Change Summary
app/client/src/sagas/EvalErrorHandler.ts	Replaced Sentry.captureMessage(error.message) with captureException(error, { errorName: "UpdateDataTreeError" }) for improved error reporting in the evalErrorHandler saga.

Sequence Diagram(s)

sequenceDiagram
    participant Saga as evalErrorHandler Saga
    participant Logger as Local Logger
    participant Sentry as Error Tracking

    Saga->>Logger: Log error locally
    Saga->>Sentry: captureException(error, { errorName: "UpdateDataTreeError" })

Loading

Possibly related PRs

• chore: log evaluation error logs and push execption to sentry #40170: Refines error reporting in evalErrorHandler by enhancing Sentry exception capturing, directly related to the same saga.

Suggested labels

skip-changelog, ok-to-test

Suggested reviewers

• rajatagrawal

Poem

When errors arise in the data tree’s flow,
Now full exceptions to Sentry we throw!
With error names tagged,
No detail is lagged—
So debugging’s a breeze, and insights will grow.
🌳🐞

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f9d2e2f and ef3a074.

📒 Files selected for processing (1)

• app/client/src/sagas/EvalErrorHandler.ts (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

app/client/src/sagas/EvalErrorHandler.ts (2)

app/client/src/instrumentation/sendFaroErrors.ts (1)

• captureException (4-19)

app/client/src/utils/Analytics/sentry.ts (1)

• captureException (19-21)

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

• GitHub Check: client-unit-tests / client-unit-tests
• GitHub Check: client-prettier / prettier-check
• GitHub Check: client-lint / client-lint
• GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
• GitHub Check: client-build / client-build

🔇 Additional comments (1)

app/client/src/sagas/EvalErrorHandler.ts (1)

314-314: Improved error reporting with Faro implementation

The change correctly replaces Sentry.captureMessage with captureException, which now sends the complete error object rather than just the message string. This provides more comprehensive error context for debugging with the appropriate error name tag.

✨ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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

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.