Closed xtuchyna closed 2 years ago
/hold
/cc @goern
Looking at the original issue, it has many goals and extensions, so it is not clear what follows. What should we prioritize and do next, should we split the Issue or just complete it in this PR (which could be a blocker for basic metrics that are already implemented) ? @goern @Gkrumbach07 @codificat
Added usage indicators
Closes #598 #599 #600
/unhold
/cc @Gkrumbach07 @goern
is this ready to merge? I didnt have a look at the code, but would like to see what the metrics report or dashboard looks like.
The usage metrics look good. Did you plan on exporting a aggregate output of each repos usage, or will that be the job of the dashboard? @xtuchyna
@Gkrumbach07 we can definitely add it to the SLI/SLO dataframe or create an aggregate output on its own
@goern all the data file examples this functionality generates are attached to the PR description, and yes I feel like this can be merged
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: xtuchyna
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Related Issues and Dependencies
Closes #572 #598 #599 #600
This introduces a breaking change
This should yield a new module release
This Pull Request implements
Currently the data is stored as a csv in following format (tested only on 3 repositories
thoth-station/mi-scheduler,thoth-station/mi,thoth-station/thoth-github-action
, with update manager left out)Kebechet SLI/SLO metrics
at location
./srcopsmetrics/metrics/kebechet_sli_slo.csv
Kebechet usage indicators
at location
./srcopsmetrics/metrics/kebechet_sli_slo.csv
Example file
sli/slo metrics file
kebechet_sli_slo.csv
usage count file
kebechet_usage_counts.csv