Expose workflow job metrics via new actions-metrics-server #2057
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mumoshu
changed the title
mumoshu
changed the title
toast-gear
approved these changes
Dec 9, 2022
|
@toast-gear Thanks a lot for reviewing! |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an enhanced version of @ColinHeathman's #1814, which introduces a dedicated command/application for receiving workflow job webhook events and exposing Prometheus metrics, so that you can scale the github-webhook-server and the new actions-metrics-server separately and independently.
This also updates the Helm chart to accept new values under
actionsMetricsandactionsMetricsServerfor configuringServiceMonitorand a set of K8s resources for the actions-metrics-server separately.I'm submitting this as a new pull request, because for whatever reason I was unable to push/force-push to the source branch of #1814. (Perhaps it's due to that the branch is under the author's GitHub organization, not the author's account?