There's an idea to add label to current sensor to distinguish storage type. Migration and numerous dashboards and alerts must be addressed. (Label might be bad idea)
In order to make separated storage consumtion and quota info available in embedded ui, let's extend DiskSpaceUsage section with consumtion by type and DatabaseQuotas section with quotas by type.
Old quotas and consumption must be kept for migration purposes.
besides, we decided to sum consumtion on poolkinds nvme as ssd report it to resources.storage.used_bytes.ssd metric.
jepett0
commented
4 months ago
According to https://ydb.tech/docs/en/troubleshooting/monitoring#resources currently YDB provides public sensors for quota and usage that are combined for all storage types:
resources.storage.used_bytes resources.storage.limit_bytes
There's an idea to add label to current sensor to distinguish storage type. Migration and numerous dashboards and alerts must be addressed. (Label might be bad idea)
In order to make separated storage consumtion and quota info available in embedded ui, let's extend DiskSpaceUsage section with consumtion by type and DatabaseQuotas section with quotas by type.
Old quotas and consumption must be kept for migration purposes.
besides, we decided to sum consumtion on poolkinds nvme as ssd report it to resources.storage.used_bytes.ssd metric.
PoolKinds with names rot are equivalent to hdd