Skip to content

fix(chipingress): set explicit bucket boundaries for request_size_bytes histogram#2136

Open
pkcll wants to merge 2 commits into
mainfrom
chipingress-batch-req-size-hist-buckets
Open

fix(chipingress): set explicit bucket boundaries for request_size_bytes histogram#2136
pkcll wants to merge 2 commits into
mainfrom
chipingress-batch-req-size-hist-buckets

Conversation

@pkcll

@pkcll pkcll commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Set explicit bucket boundaries for chip_ingress_batch_request_size_bytes_bucket histogram

@pkcll pkcll requested a review from a team as a code owner June 9, 2026 05:55
Copilot AI review requested due to automatic review settings June 9, 2026 05:55
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

👋 pkcll, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

📊 API Diff Results

No changes detected for module github.com/smartcontractkit/chainlink-common/pkg/chipingress

View full report

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the Chip Ingress batch client metrics to use explicit histogram bucket boundaries for the PublishBatch request size (bytes), improving the usefulness/consistency of the exported *_bucket series.

Changes:

  • Add explicit bucket boundaries (1 KiB → 10 MiB) for chip_ingress.batch.request_size_bytes histogram.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@pkcll pkcll force-pushed the chipingress-batch-req-size-hist-buckets branch from 5321e66 to 824d8d5 Compare June 9, 2026 06:07
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.

5 participants