Add metrics to the write-cache #312
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#312
Loading…
Add table
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 will help to understand system state in the test.
Need write-cache fill metric to observe it in grafana while test is runningto Add metrics to the write-cacheThe title mentioned fill metric before, but we sure can think of others too.
Suggestion:
hit/miss counters, hit counter with source type label - db or fstree
put counter with source type label
delete counter with source type label
flushed counter with source type label
actual objects count - it's look like 2 - (3 + 4), but i think it should be separate counter to not handle metric overflow cases
put, get & head, delete duration
mode (readonly, readwrite, etc)
estimated size
Done with #378