hiero-ledger / hiero-ledger/hiero-consensus-node

Redesign of RunningAverageMetric and SpeedometerMetric

Open
#5,283 2 comments 0 reactions 0 assignees View on GitHub
Base Metrics Feature Enhancement P2 Platform
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

Redesign of RunningAverageMetric and SpeedometerMetric as discussed:

We will NOT calculate a running average anymore. Instead we are going to aggregate all entries between two snapshot (currently every 3 sec.). If a value (mean, max etc.) is requested from a RunningAverageMetric or SpeedometerMetric, we do not return the current state, but the value from the last snapshot.

RunningAverageMetric will continue to gather mean average, minimum, maximum, and standard deviation. SpeedometerMetric will only gather mean average and standard deviation.

The history will not be handled by these classes anymore. Instead it will be handled were needed based on Snapshots.

Contributor guide

Open the contributing guide

Research direction

Locate RunningAverageMetric and SpeedometerMetric and trace how their snapshots and history are currently handled. Verify the snapshot interval and existing metric tests before separating aggregation from history; done means values come from the last snapshot, with the specified statistics retained for each metric.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
observability-sre
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.