Figure out Garage metrics #30
Labels
No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: afnix/infra#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Garage itself has a few metrics, but not the interesting ones like disk space growth over time. We should figure out how to collect those without grinding everything to a halt.
https://gitlab.com/codingJWilliams/garagehq-stats-exporter exists and has more information than the basic endpoint
Was mentioned on Matrix, but good to have a record here. Also, requires admin access :(
Unlikely to happen until S3 is migrated off of my private infra. I could possibly be convinced to add an exporter if it can be restricted to a given set of buckets, and if it's not too much work to maintain on my systems.
Given that the exporter is 30 lines of straightforward python, I can rewrite it tomorrow to add a filter for exported buckets
Tracking issues in Garage repo:
https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/827
https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/420
Modifying the exporter is probably fastest here
I did the rewrite, but the original code has no license. I will ping the author and demand a license, in the meantime, we can go ahead without delroth necessarily because c.f.o. is being phased out.