`.count` vs `.usage` vs `.size`

looking at current usage:

.count

system.processes.count
jvm.threads.count
jvm.buffer.count
jvm.classes.count (Rename jvm.classes.current_loaded to jvm.classes.count #60)

.usage

db.client.connections.usage / db.client.connections.max
hw.gpu.memory.usage / hw.gpu.memory.utilization / hw.gpu.memory.usage
hw.logical_disk.usage / hw.logical_disk.utilization / hw.logical_disk.limit
process.memory.usage
jvm.memory.usage / jvm.memory.limit
jvm.buffer.usage / jvm.buffer.limit
system.memory.usage / system.memory.utilization
system.paging.usage / system.paging.utilization
system.filesystem.usage / system.filesystem.utilization

.usage appears to be primarily used for metrics with unit Byte

interestingly, jvm.buffers.* has both .count (number of buffers) and .usage (bytes used by those buffers), which makes it confusing which one jvm.buffers.limit applies to (at least without looking at the unit for jvm.buffers.limit)

.size

http.server.request.size
http.server.response.size
http.client.request.size
http.client.response.size
rpc.server.request.size
rpc.server.response.size
rpc.client.request.size
rpc.client.response.size
hw.physical_disk.size

.count vs .usage vs .size

`.count` vs `.usage` vs `.size`

Document common metric names and when they should be used #211

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions