Adjust get_webstat_metrics.py for time-bound epochs #65

New issue

Closed

opened 2025-12-28 18:13:57 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:13:57 +00:00

Owner

Originally created by @roman-khimov on GitHub (Jun 20, 2025).

Originally assigned to: @mike-petrov on GitHub.

I'm always frustrated when status can display misleading data. Epochs will soon be time-bound, not block count-bound. Which makes duration (3600 usually) seconds and we should be comparing time passed since the last epoch tick. Some tolerance should be allowed like 5% (3m for 1h epochs, seems to be ok).

Describe the solution you'd like

Fix get_webstat_metrics.py to follow the logic above. Ask @carpawell for details of how it works and where to get which data.

Additional context

https://github.com/nspcc-dev/neofs-node/pull/3404
https://github.com/nspcc-dev/neofs-node/issues/3402
https://github.com/nspcc-dev/neofs-api/pull/331

Originally created by @roman-khimov on GitHub (Jun 20, 2025). Originally assigned to: @mike-petrov on GitHub. ## Is your feature request related to a problem? Please describe. I'm always frustrated when status can display misleading data. Epochs will soon be time-bound, not block count-bound. Which makes duration (3600 usually) seconds and we should be comparing time passed since the last epoch tick. Some tolerance should be allowed like 5% (3m for 1h epochs, seems to be ok). ## Describe the solution you'd like Fix get_webstat_metrics.py to follow the logic above. Ask @carpawell for details of how it works and where to get which data. ## Additional context https://github.com/nspcc-dev/neofs-node/pull/3404 https://github.com/nspcc-dev/neofs-node/issues/3402 https://github.com/nspcc-dev/neofs-api/pull/331