-
Notifications
You must be signed in to change notification settings - Fork 567
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
[viewer api] quota and consumption for hdd storage types must be returned #4611
Comments
The expected result looks like this.
I'm going to remove The pool type is specified in the config. It's a |
I would like all the logic for calculating values for the |
Recently, we agreed to use soft quota, so our diagnostics will match with data that ydb provides to monitoring services (soft quota as limit). So we need soft quota as limit as well. I suggested to add both quotas in other ticket, so there will be flexibility to change values, when needed. Currently, hard quota is not needed at all. At the same time, we discussed displaying all data as table in extended info, where there will be not only consumption for every disk type, but also all quotas (both soft and hard) |
@artemmufazalov There is an issue with the sizes and limits not being separated by storage type as they were before. I would like to keep only one field, The sizes and limits that can't be separated by storage type are still accessible through other fields. They are not divided by storage type: Metrics.Storage - Blob storage size so the final response could look like this
|
@StekPerepolnen, here I mean blob and tablet storage, we need both. We use tablet storage if quotas are set and blob storage size and limits otherwise |
have to be TabletStorage and DatabaseStorage |
As a follow-up for #3430
tenantInfo/storageUsage
response.cold-visits
with HDD storage without storage database quotas doesn't have HDD info intenantInfo/storageUsage
response. But must have info about quotas and consumption of attached HDD storageThe text was updated successfully, but these errors were encountered: