-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat(tiering): Basic metrics #6086
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| }, | ||
| "disableTextWrap": false, | ||
| "editorMode": "builder", | ||
| "expr": "rate(dragonfly_tiered_hits[$__rate_interval])", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably should be an irate
|
|
||
| // Tiered metrics | ||
| { | ||
| AppendMetricWithoutLabels("tiered_entries", "Tiered entries", total.tiered_entries, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice grouping.
romange
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about cool memory? we have memory_by_class_bytes - can you add anything accountable that contributes to memory usage?
btw, while you are at it, can you please also add m.search_stats.used_memory to memory_by_class_bytes that we missed.
Shouldn't be anything, as even cold_storage_bytes is part of just object memory usage.
Added |
Basicc prometheus metrics for tiering
