chore: removed code

[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="@tag.All"

🔍 Cypress test results

Caution

🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11321455639
Commit: cc4ac6d
Cypress dashboard.
Tags: @tag.All
Spec:
The following are new failures, please fix them before merging the PR:

1. cypress/e2e/Regression/ClientSide/EmbedSettings/EmbedSettings_spec.js
2. cypress/e2e/Regression/ClientSide/Github/EnableGithub_spec.ts
3. cypress/e2e/Regression/ClientSide/Linting/ErrorReporting_spec.ts
4. cypress/e2e/Regression/ServerSide/ApiTests/API_Edit_spec.js

List of identified flaky tests.

---

Mon, 14 Oct 2024 06:26:15 UTC

Communication

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

• Yes
• No

Summary by CodeRabbit

• New Features

  • Integrated New Relic for enhanced telemetry tracking.

• Bug Fixes

  • Removed the Heartbeat component to streamline application performance and rendering logic.

• Chores

  • Cleaned up unnecessary variables related to component rendering.

[coderabbitai]

Walkthrough

This pull request involves the deletion of the Heartbeat.tsx file, which contained a React component responsible for sending periodic heartbeat signals. Additionally, the index.tsx file was modified to integrate New Relic for telemetry, removing the cloudHosting and isProduction variables that previously controlled the rendering of the Heartbeat component. As a result, the application’s rendering logic has been simplified while enhancing its telemetry capabilities.

Changes

File	Change Summary
app/client/src/Heartbeat.tsx	Component removed: Heartbeat responsible for sending heartbeat signals.
app/client/src/index.tsx	Added New Relic configuration; removed cloudHosting and isProduction variables; simplified rendering logic.

Possibly related PRs

• Chore: added heartbeat for monitoring #36704: This PR adds a new Heartbeat component, which is directly related to the deletion of the Heartbeat.tsx file in the main PR, indicating a complete removal of the heartbeat functionality.
• chore: Page load instrumentation: add network and device info to page load spans #36395: The changes in this PR to index.tsx involve the removal of the cloudHosting and isProduction variables, which were previously used to conditionally render the Heartbeat component, thus linking it to the main PR's changes.
• fix: TBP for the invalid usage of GH workflow_dispatch action #36429: This PR modifies the workflow related to the pg branch, which may indirectly relate to the overall application structure and its components, including the Heartbeat functionality that was removed in the main PR.

Suggested labels

skip-changelog, ok-to-test

Suggested reviewers

• sharat87
• AnaghHegde

In the code's heart, a signal did play,
Sending its whispers, day after day.
But now it has vanished, like mist in the sun,
New Relic's here, and the changes are done!
A simpler path, with telemetry bright,
Our app shines anew, oh what a delight! 🌟

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between e03522f and cc4ac6d.

📒 Files selected for processing (2)

• app/client/src/Heartbeat.tsx (0 hunks)
• app/client/src/index.tsx (0 hunks)

💤 Files with no reviewable changes (2)

• app/client/src/Heartbeat.tsx
• app/client/src/index.tsx

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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