[EPIC] Metric collection
Closed this issue · 7 comments
- Identify relevant repos to fetch metrics
- Split metric collection from different sources into different issues
- Store metrics (via MI scheduler, Ceph)
Identify relevant repos to fetch metrics
Please see https://github.com/open-services-group/community/blob/main/sigs.yaml which contains a list of all the repo's currently associated with the OSG org.
Here is an example: https://github.com/open-services-group/community/blob/245511c0abeca780747c903a1368a54091a5dd22/sigs.yaml#L44-L51
Store metrics (via Augur, Ceph)
Is this still the approach? I thought we had discussed using the MI scheduler?
For reference: As part of AI4CI, we used Github PR data from the openshift/origin repository obtained using the MI tool and we visualized the statistics, KPIs, metrics such as contributors over time, merge statistics over time, etc. on this SuperSet dashboard.
We also had plans on analyzing the Issues data, which is currently being discussed here
Store metrics (via Augur, Ceph)
Is this still the approach? I thought we had discussed using the MI scheduler?
yes we will proceed with MI scheduler, updated the description
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/close
@hemajv: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.