action #156061
Updated by JERiveraMoya about 1 year ago
## Motivation One additional metric for Grafana could be the number of YAML files that we have in the `schedule/yam` folder, reflecting what we have refactored already on the tickets to reduce the overall amount of YAML schedules in openQA. **It is is really important to not break [our our current dashboard](https://monitor.qa.suse.de/d/d2bf593c-835c-42db-a1b1-bf77ab2f82e9/yam-metrics?from=1705878000000&to=now&orgId=1), dashboard, that we don't loose any existing information so we can present metrics to management any time. If the person working in this ticket needs a sandbox env. for that it should be created.** ## Additional info Despite the existence of a [GitHub data source](https://grafana.com/grafana/plugins/grafana-github-datasource/) in Grafana the job is probaly easier to achieve by a small custom script that does a frequent checkout of the GitHub repo master branch and then does a ``` find schedule/yam -name "*.yaml" | wc -l ``` to obtain the count of YAML files. This count then should be sent to InfluxDB (easy by using Telegraf that executes frequently as a wrapper for that script), so that Grafana can use it. ## Acceptance criteria - **AC1:** Create custom script to get the measurement - **AC2:** Create a Telegraf wrapper that calls this script by a defined schedule (e.g. daily) and pipes it to InfluxDB - **AC3:** Create a panel in Grafana that visualizes the measurements either as a time series (to see the progress) or a gauge (to see the current value)