Think out badger metrics and traces #583
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 project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#583
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
It has something exported via the https://github.com/dgraph-io/badger/blob/main/y/metrics.go
It also has traces (see
runGC
function), though it creates a new context and it uses another package for this.I suggest disabling traces and, possibly, having
expvar
reexported via prometheus. Note that in this case metrics presense in config-dependent and may miss from the output of./scripts/export-metrics
script -- need to think what we do here. Another option is to disable metrics.Badger wc is disabled, no longer actual.