Add GC metrics #407
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#407
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:feat/gc-metrics"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #376
Signed-off-by: Dmitrii Stepanov d.stepanov@yadro.com
@ -0,0 +40,4 @@
func newGCMetrics() *gcMetrics {
return &gcMetrics{
runDuration: newCounterVec(prometheus.CounterOpts{
Counter vector used for duration because
GC can run 1 second or more than 1 minute, so using buckets will give us less information than counter
GC runs as single process in the moment for shard
@ -108,0 +108,4 @@
shard.WithGCMetrics(
&gcMetrics{
storage: e.metrics.GC(),
shardID: id.String(),
What about extending shard metrics interface with a
GC()
method?Shard metrics look too complex already i think. So I would leave it like that, if you don't insist.
I mean the choice is between having a single "metrics" interface or multiple metric-related parameters, which feels klunky.
I don't insist, though.
@ -0,0 +61,4 @@
inhumedCounter: newCounterVec(prometheus.CounterOpts{
Namespace: namespace,
Subsystem: gcSubsystem,
Name: "marked_to_removal_objects_count",
for removal?
Also, I think using
inhumed_objects_count
is also fine.inhumed_objects_count
was the first option. But in spec it callsmark
for removal - fixed
4a8ff6136f
to5c8e6215f8