Use the PD MinIO S3 usage page to review stored bytes, object counts and service history. Read the collection time alongside the number; a normal sample can lag behind a recent upload or deletion.

Read the latest measurement

1. Open the intended service’s Usage section.
2. Inspect storage used, quota, object count and the latest collection time.
3. Review the history and current access mode.
4. Check Activity for collection failures when the figure remains old.

Scheduled collection normally uses MinIO’s background scanner. A fresh bucket not yet represented can need direct object counting. Counts and versions may be represented differently, so do not treat a displayed object count as a complete file-by-file recovery inventory.

Use Refresh where appropriate

The client Refresh action requests a bounded direct measurement, including retained versions where applicable. It is rate limited. Large buckets can exceed the interactive limit; in that case the module refuses a short partial count and the last good reading remains available.

Confirm normal module jobs and the platform cron are running. Repeated clicking cannot repair a failed administration permission or make a large measurement complete instantly. After freeing storage, a successful refresh can also update quota enforcement; inspect the actual result.

Interpret the figure for billing

Blesta does not provide native disk-usage overage invoicing for these services. Price the package’s storage tiers and use the module’s quota readings and notifications for follow-up.

The module does not provide per-bucket Class A/Class B operation counters for MinIO. Review the quota guide for an upload pause and versioning when deleting current objects did not reduce bytes. Retain sample times and redacted errors while your hosting team checks collection, without customer object listings or credentials.

Some failed per-bucket measurements can be skipped while other buckets still contribute to a new sample. A fresh timestamp or successful Refresh is therefore not proof that every service bucket was counted. If usage drops unexpectedly or a quota pause changes after a measurement error, have your storage administrator compare the intended bucket set and actual stored data before treating the total as complete or assuming space was freed.

Check the usage sample

Your hosting team should compare the original collection or Refresh time, latest successful sample and Activity error with the actual service and bucket scope. Scheduled scanner figures and a bounded live measurement can differ; a large live walk can be refused while the last good reading remains. Check normal scheduled work and administration permissions instead of clicking repeatedly. Usage is not a complete recovery inventory or proof that the platform generated an overage invoice.

See the PD MinIO S3 Blesta guide for related tasks, or explore the module.