Add metrics for logical size #763

Closed
opened 2023-10-30 11:35:04 +00:00 by fyrchik · 4 comments
Owner

container_size_bytes should have a label kind=physical/kind=logical
container_objects_total should have label cid (and kind too)
May be we could reuse objects_total metric with shard label, but imo it is better as container_objects_total -- they are used for different purposes.

`container_size_bytes` should have a label `kind=physical`/`kind=logical` `container_objects_total` should have label `cid` (and kind too) May be we could reuse `objects_total` metric with shard label, but imo it is better as container_objects_total -- they are used for different purposes.
fyrchik added the
discussion
frostfs-node
observability
labels 2023-10-30 11:35:04 +00:00
fyrchik added this to the v0.38.0 milestone 2023-10-31 10:34:53 +00:00
dstepanov-yadro self-assigned this 2023-10-31 17:26:16 +00:00
dstepanov-yadro removed their assignment 2023-10-31 17:26:25 +00:00
dstepanov-yadro self-assigned this 2023-10-31 17:26:38 +00:00

@fyrchik does some migration procedure required? Now logical size is stored.

Also am i right that container_objects_total is new metric? Now only object per shard are awailable.

@fyrchik does some migration procedure required? Now logical size is stored. Also am i right that `container_objects_total` is new metric? Now only object per shard are awailable.
Author
Owner

What migration do you have in mind? We already store logical capacity of a container
We could also store physical one.

container_objects_total is a new metric

What migration do you have in mind? We already store logical capacity of a container We could also store physical one. `container_objects_total` is a new metric
Author
Owner

We need logical sizes for hard quotes, let's just do container_objects_total now

We need logical sizes for hard quotes, let's just do `container_objects_total` now

@fyrchik How about renaming kind label with physical and logical values in the new metric container_objects_total to, for example, available=true/false.

For example, if container have 5 objects, but 2 of them are inhumed, now counters will be

container_objects_total {kind=physical} 5
container_objects_total {kind=logical} 3

After change it will be

container_objects_total {available=true} 3
container_objects_total {available=false} 2

So available=true counter equals kind=logical counter, available=false = kind=physical - kind=logical

@fyrchik How about renaming `kind` label with `physical` and `logical` values in the new metric `container_objects_total` to, for example, `available=true/false`. For example, if container have 5 objects, but 2 of them are inhumed, now counters will be ``` container_objects_total {kind=physical} 5 container_objects_total {kind=logical} 3 ``` After change it will be ``` container_objects_total {available=true} 3 container_objects_total {available=false} 2 ``` So `available=true` counter equals `kind=logical` counter, `available=false` = `kind=physical` - `kind=logical`
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#763
No description provided.