nspcc-dev / nspcc-dev/neofs-node

Add shard free space to metrics

Open
#3,950 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement I3 neofs-storage S4 U4
Dominant language
Go
Stars
38
Forks
51
Avg merge
1d 20h
Merged PRs (30d)
38

Description

Is your feature request related to a problem? Please describe.

Required to calculate free space in a cluster.

Describe the solution you'd like

# TYPE neofs_node_engine_freespace gauge
neofs_node_engine_freespace{shard="Jjam495aBJubsKkRXTYqJz"} 1.609826304e+11
neofs_node_engine_freespace{shard="RU5y6bserpbKNLPdXi9rji"} 1.609826304e+11

Describe alternatives you've considered

Add shard mountpoint to metrics.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by locating the code that exposes node engine shard metrics and inspect how existing metrics are registered and collected; done means the free-space gauge appears once per shard with the requested label and value, verified through the relevant metrics test or scrape.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.