Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(transfer): move telemetry to internal folder #6513

Merged
merged 5 commits into from
Jun 5, 2024

Conversation

gjermundgaraba
Copy link
Contributor

@gjermundgaraba gjermundgaraba commented Jun 5, 2024

Description

Moves the big telemetry functions that take a lot of real estate space in the functions where they appear into an internal telemetry package.

Part of #6425. Can serve as an example and starting point for some "good first issue" issue(s).


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against the correct branch (see CONTRIBUTING.md).
  • Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/).
  • Added relevant godoc comments.
  • Provide a conventional commit message to follow the repository standards.
  • Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
  • Re-reviewed Files changed in the GitHub PR explorer.
  • Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

  • New Features
    • Introduced telemetry reporting for transfers and packet receptions, enhancing monitoring and analytics within the app.

Copy link
Contributor

coderabbitai bot commented Jun 5, 2024

Walkthrough

The recent changes introduce telemetry functions to the Cosmos SDK application, specifically for tracking transfers and packet receptions within the IBC module. These additions involve new functions in the telemetry.go file for reporting transfer and packet reception metrics. Corresponding changes in relay.go replace existing telemetry calls with the newly added internal telemetry functions.

Changes

File Path Change Summary
modules/apps/transfer/internal/telemetry/telemetry.go Added functions to report transfer telemetry and packet reception telemetry.
modules/apps/transfer/keeper/relay.go Updated import statements and replaced telemetry-related functions with calls to internal telemetry.

Sequence Diagram(s) (Beta)

sequenceDiagram
    participant User
    participant App
    participant Telemetry

    User ->> App: Initiates Transfer
    App ->> Telemetry: ReportTransferTelemetry(tokens, labels)
    App ->> User: Transfer Confirmation

    User ->> App: Receives Packet
    App ->> Telemetry: ReportOnRecvPacketTelemetry(transferAmount, denomPath, labels)
    App ->> User: Packet Reception Confirmation
Loading

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

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: 2

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6e9128f and f01a02b.

Files selected for processing (2)
  • modules/apps/transfer/internal/telemetry/telemetry.go (1 hunks)
  • modules/apps/transfer/keeper/relay.go (5 hunks)
Additional context used
Path-based instructions (2)
modules/apps/transfer/internal/telemetry/telemetry.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

modules/apps/transfer/keeper/relay.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

Additional comments not posted (2)
modules/apps/transfer/keeper/relay.go (2)

Line range hint 7-16: Updated import statements align with the PR's objective to centralize telemetry logic.

The removal of the alias for go-metrics and the addition of internaltelemetry are consistent with the changes in the telemetry functions.


151-151: Integration of new telemetry functions is correctly implemented.

The deferred calls to ReportTransferTelemetry and ReportOnRecvPacketTelemetry at the end of the respective functions ensure that telemetry is recorded after all other operations are completed, which is a good practice.

Also applies to: 215-215, 256-256

Comment on lines +14 to +31
func ReportTransferTelemetry(tokens types.Tokens, labels []metrics.Label) {
for _, token := range tokens {
amount, ok := sdkmath.NewIntFromString(token.Amount)
if ok && amount.IsInt64() {
telemetry.SetGaugeWithLabels(
[]string{"tx", "msg", "ibc", "transfer"},
float32(amount.Int64()),
[]metrics.Label{telemetry.NewLabel(coretypes.LabelDenom, token.Denom.Path())},
)
}
}

telemetry.IncrCounterWithLabels(
[]string{"ibc", types.ModuleName, "send"},
1,
labels,
)
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider handling the case where amount.IsInt64() returns false.

Currently, if amount.IsInt64() returns false, the function silently skips recording telemetry for that token. It might be beneficial to log this occurrence or handle it in a way that ensures visibility of the issue.

Comment on lines +33 to +47
func ReportOnRecvPacketTelemetry(transferAmount sdkmath.Int, denomPath string, labels []metrics.Label) {
if transferAmount.IsInt64() {
telemetry.SetGaugeWithLabels(
[]string{"ibc", types.ModuleName, "packet", "receive"},
float32(transferAmount.Int64()),
[]metrics.Label{telemetry.NewLabel(coretypes.LabelDenom, denomPath)},
)
}

telemetry.IncrCounterWithLabels(
[]string{"ibc", types.ModuleName, "receive"},
1,
labels,
)
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure robust error handling when transferAmount.IsInt64() returns false.

Similar to ReportTransferTelemetry, this function does not handle the case where transferAmount.IsInt64() returns false. Consider adding error logging or another form of notification to handle this scenario effectively.

Copy link
Contributor

@colin-axner colin-axner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love this change a lot! Thank you!

Copy link

sonarcloud bot commented Jun 5, 2024

Quality Gate Failed Quality Gate failed for 'ibc-go'

Failed conditions
60.6% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

Copy link
Contributor

@DimitrisJim DimitrisJim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great, very nice to see this refactored out!

@DimitrisJim DimitrisJim enabled auto-merge (squash) June 5, 2024 16:04
@DimitrisJim DimitrisJim merged commit f53f4c0 into main Jun 5, 2024
71 of 75 checks passed
@DimitrisJim DimitrisJim deleted the gjermund/move-transfer-telemetry-to-internal branch June 5, 2024 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants