feat(da): submitted batch size metric

[srene]

PR Standards

Opening a pull request should be able to meet the following requirements

--

PR naming convention: https://hackmd.io/@nZpxHZ0CT7O5ngTp0TP9mg/HJP_jrm7A

---

Close #1007

<-- Briefly describe the content of this pull request -->

For Author:

• Targeted PR against correct branch
• included the correct type prefix in the PR title
• Linked to Github issue with discussion and accepted design
• Targets only one github issue
• Wrote unit and integration tests
• All CI checks have passed
• Added relevant godoc comments

---

For Reviewer:

• confirmed the correct type prefix in the PR title
• Reviewers assigned
• confirmed all author checklist items have been addressed

---

After reviewer approval:

• In case targets main branch, PR should be squashed and merged.
• In case PR targets a release branch, PR should be rebased.

Summary by CodeRabbit

• New Features

  • Introduced enhanced logging for batch submissions, now including the size of the batch.
  • Added a new metric to track the size of the last submitted batch for improved performance monitoring.

• Bug Fixes

  • None identified in this release.

• Documentation

  • Updated descriptions for new logging and metric capabilities.

[coderabbitai]

Walkthrough

The changes enhance logging and monitoring in the CreateAndSubmitBatch method of the Manager struct. The batch size is now logged when created, and a new Prometheus gauge tracks the size of the last submitted batch. These improvements facilitate better observability and debugging without altering existing functionality, enabling more efficient performance tracking in decentralized applications.

Changes

Files	Change Summary
block/submit.go	Enhanced logging in CreateAndSubmitBatch to include batch size and updated metrics tracking.
types/metrics.go	Introduced LastBatchSubmittedBytes gauge for monitoring the size of the last submitted batch.

Poem

In the meadow, bouncing bright,
Changes come, a lovely sight!
With batch sizes logged in cheer,
Metrics dance, no need to fear.
Hop along, dear friends so true,
Monitoring’s magic, just for you! 🐰✨

---

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

[coderabbitai]

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)

block/submit.go (1)

156-157: Enhanced logging with batch size information.

The log message now includes the batch size, providing better insight into batch creation. Ensure this level of detail is appropriate for the current logging level.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7ee8303 and 8ab3660.

Files selected for processing (2)

• block/submit.go (1 hunks)
• types/metrics.go (1 hunks)

Additional comments not posted (2)

types/metrics.go (1)

38-41: LGTM! New metric added for batch size tracking.

The addition of LastBatchSubmittedBytes enhances observability by tracking the size of the last submitted batch. The metadata is appropriately defined.

block/submit.go (1)

157-157: Metric update for batch size tracking.

The LastBatchSubmittedBytes metric is updated with the batch size, enhancing monitoring capabilities.