Skip to content

chore: code split for consolidated api span names to add module instances and entities in EE #38804

Merged
ApekshaBhosale merged 1 commit intoreleasefrom
ce-modules-entities-span-names
Jan 27, 2025
Merged

chore: code split for consolidated api span names to add module instances and entities in EE #38804
ApekshaBhosale merged 1 commit intoreleasefrom
ce-modules-entities-span-names

Conversation

@ApekshaBhosale
Copy link
Contributor

@ApekshaBhosale ApekshaBhosale commented Jan 22, 2025

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

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12945714399
Commit: f794c00
Cypress dashboard.
Tags: @tag.All
Spec:


Fri, 24 Jan 2025 12:14:23 UTC

Communication

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

  • Yes
  • No

Summary by CodeRabbit

  • Refactor

    • Restructured span naming constants for consolidated API tracing
    • Introduced a new base class ConsolidatedApiSpanNamesCE to centralize span name definitions
    • Updated inheritance structure for ConsolidatedApiSpanNames
  • New Features

    • Added comprehensive span naming constants for various application components
    • Standardized span naming with appsmith. prefix for improved tracing consistency

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 22, 2025

Walkthrough

The pull request introduces a new class ConsolidatedApiSpanNamesCE in the com.appsmith.external.constants.spans.ce package, which defines a comprehensive set of span name constants for performance tracing. The existing ConsolidatedApiSpanNames class has been refactored to extend this new class, effectively centralizing and standardizing span naming conventions across the application's tracing infrastructure.

Changes

File Change Summary
app/server/appsmith-interfaces/src/main/java/.../ConsolidatedApiSpanNames.java Refactored to extend ConsolidatedApiSpanNamesCE, removing local constant definitions
app/server/appsmith-interfaces/src/main/java/.../ce/ConsolidatedApiSpanNamesCE.java New class added with multiple public static final span name constants prefixed with appsmith.

Possibly related PRs

Suggested labels

skip-changelog, ok-to-test, Integrations Pod General, Query & JS Pod

Suggested reviewers

  • nidhi-nair
  • sondermanish

Poem

Spans of tracing, constants bright,
Naming patterns taking flight!
From CE to interface they go,
Performance tracking's gentle flow
Code poetry in Java's embrace 🚀

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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
🪧 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. (Beta)
  • @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.

@github-actions github-actions bot added the skip-changelog Adding this label to a PR prevents it from being listed in the changelog label Jan 22, 2025
Copy link
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: 0

🧹 Nitpick comments (1)
app/server/appsmith-interfaces/src/main/java/com/appsmith/external/constants/spans/ce/ConsolidatedApiSpanNamesCE.java (1)

10-34: Consider grouping related constants using nested classes.

While the constants are well-named, consider organizing related spans (e.g., pages, actions, datasources) into nested static classes for better maintainability.

Example refactoring:

 public class ConsolidatedApiSpanNamesCE {
     public static final String CONSOLIDATED_API_PREFIX = APPSMITH_SPAN_PREFIX + "consolidated-api.";
     public static final String VIEW = "view.";
     public static final String EDIT = "edit.";
     public static final String ROOT = "root";
     public static final String CONSOLIDATED_API_ROOT_EDIT = CONSOLIDATED_API_PREFIX + EDIT + ROOT;
     public static final String CONSOLIDATED_API_ROOT_VIEW = CONSOLIDATED_API_PREFIX + VIEW + ROOT;
 
+    public static class UserSpans {
         public static final String USER_PROFILE_SPAN = "user_profile";
         public static final String FEATURE_FLAG_SPAN = "feature_flag";
         public static final String TENANT_SPAN = "tenant";
+    }
 
+    public static class PageSpans {
         public static final String PAGES_SPAN = "pages";
         public static final String PAGES_DSL_SPAN = "pages_dsl_list";
         public static final String CURRENT_PAGE_SPAN = "current_page";
+    }
 
     // ... similar groupings for other related constants
 }
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b14669e and f794c00.

📒 Files selected for processing (2)
  • app/server/appsmith-interfaces/src/main/java/com/appsmith/external/constants/spans/ConsolidatedApiSpanNames.java (1 hunks)
  • app/server/appsmith-interfaces/src/main/java/com/appsmith/external/constants/spans/ce/ConsolidatedApiSpanNamesCE.java (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: server-spotless / spotless-check
  • GitHub Check: server-unit-tests / server-unit-tests
🔇 Additional comments (2)
app/server/appsmith-interfaces/src/main/java/com/appsmith/external/constants/spans/ConsolidatedApiSpanNames.java (1)

3-3: Clean implementation of code split.

The refactoring to extend ConsolidatedApiSpanNamesCE is well-structured and maintains all functionality through inheritance.

Also applies to: 9-9

app/server/appsmith-interfaces/src/main/java/com/appsmith/external/constants/spans/ce/ConsolidatedApiSpanNamesCE.java (1)

1-8: LGTM! Well-documented span naming requirements.

The import and documentation clearly communicate the critical requirement about the appsmith. prefix.

@ApekshaBhosale ApekshaBhosale added the ok-to-test Required label for CI label Jan 24, 2025
@ApekshaBhosale ApekshaBhosale merged commit a243e97 into release Jan 27, 2025
86 checks passed
@ApekshaBhosale ApekshaBhosale deleted the ce-modules-entities-span-names branch January 27, 2025 06:47
github-actions bot pushed a commit to Zeral-Zhang/appsmith that referenced this pull request Feb 7, 2025
…nces and entities in EE (appsmithorg#38804)

## 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
<!-- This is an auto-generated comment: Cypress test results  -->
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/12945714399>
> Commit: f794c00
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=12945714399&attempt=2"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Fri, 24 Jan 2025 12:14:23 UTC
<!-- end of auto-generated comment: Cypress test results  -->


## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Refactor**
	- Restructured span naming constants for consolidated API tracing
- Introduced a new base class `ConsolidatedApiSpanNamesCE` to centralize
span name definitions
	- Updated inheritance structure for `ConsolidatedApiSpanNames`

- **New Features**
- Added comprehensive span naming constants for various application
components
- Standardized span naming with `appsmith.` prefix for improved tracing
consistency

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Required label for CI skip-changelog Adding this label to a PR prevents it from being listed in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants