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

[1.39] runtime: add metrics for receipt throughput #10944

Merged
merged 1 commit into from
Apr 4, 2024

Conversation

nagisa
Copy link
Collaborator

@nagisa nagisa commented Apr 4, 2024

And also time it takes to process them.

I kinda didn't really think about how to do this right and more about how to do it fast. My head is also not working anymore today so unless its minor typo fixes, its probably better if somebody else addresses it...

And also time it takes to process them.
@nagisa nagisa requested a review from a team as a code owner April 4, 2024 15:44
@nagisa nagisa requested review from wacban and removed request for a team April 4, 2024 15:44
@nagisa nagisa changed the title runtime: add metrics for receipt throughput [1.39] runtime: add metrics for receipt throughput Apr 4, 2024
}

/// Report statistics
pub fn report(&self, shard_id: &str) {
pub fn report(&mut self, shard_id: &str) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Where possible please use ShardUID to make it future proof (most notably for resharding as multiple shards with same ids exist at the same time). Not a blocker though.

Copy link
Contributor

@VanBarbascu VanBarbascu Apr 4, 2024

Choose a reason for hiding this comment

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

In the context of metrics, it is better to have this consistent notation for aggregation purpose. We can work on a migration plan to add ShardUID to all metrics.

@VanBarbascu VanBarbascu merged commit 16d78e7 into near:1.39.0 Apr 4, 2024
9 of 14 checks passed
@nagisa nagisa deleted the receipt-metrics branch April 5, 2024 10:56
github-merge-queue bot pushed a commit that referenced this pull request Apr 5, 2024
And also time it takes to process them.

This is a forward-port of #10944
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.

4 participants