1/19/2024 0 Comments Monit example githubWe had a fleet of ephemeral self-hosted runners with high turnover, so the Prometheus /metrics endpoint quickly became too large to parse. By default, it includes metrics with very high cardinality, such as node_id. I ran into an issue with github-actions-exporter that ended with me forking the repo. It also means that for every repository you choose to monitor, it makes an additional API call per interval, therefore using up your API quota even faster. The exporter is an imperfect solution that calls GitHub API on a loop to capture runner and workflow metrics.ĭue to the way the GitHub API is laid out, you have to explicitly specify a list of repositories for github-actions-exporter to capture workflow metrics for which is not a great experience. I used github-actions-exporter to capture some basic metrics, like workflow durations and the number of online runners connected to GitHub Enterprise. Our runners were hosted on managed Kubernetes via EKS with the Actions Runner Controller (ARC).įinally, we used Datadog for our metrics and logging needs. We had to host our runners if we wanted to use GitHub Actions. Similar to the author of the GitHub issue above, we used GitHub Enterprise Server. Of course, terms and conditions may apply – just like your unlimited home internet connection. Other engineering teams needed our help to create and maintain CI/CD pipelines.ĭuring the adoption of GitHub Actions, we gave engineers free rein to do more or less whatever they wanted on our fleet of self-hosted runners. The old support model wasn’t scaling as the engineering organization grew. We wanted teams to be more self-sufficient. One pain point I had with GitHub Actions self-hosted runners was the complete lack of ability to monitor anything related to GHA on the runners. We were required to run CI/CD pipelines on our infrastructure. I led the migration from Jenkins to GitHub Actions (GHA) at Venmo. Alerting on Builds that could use Smaller Runners.Making Metrics Useful with GHA Supervisor. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.Īny use of third-party trademarks or logos are subject to those third-party's policies. Microsoft's Trademark & Brand Guidelines. Trademarks or logos is subject to and must follow This project may contain trademarks or logos for projects, products, or services. This project has adopted the Microsoft Open Source Code of Conduct.įor more information see the Code of Conduct FAQ orĬontact with any additional questions or comments. You will only need to do this once across all repos using our CLA. When you submit a pull request, a CLA bot will automatically determine whether you need to provideĪ CLA and decorate the PR appropriately (e.g., status check, comment). Most contributions require you to agree to aĬontributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us This project welcomes contributions and suggestions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |