-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loadtest: add support for push metrics #662
loadtest: add support for push metrics #662
Conversation
Equip the test orchestrator with the ability to push metrics on execution time to a configurable remote prometheus push gateway.
Apply some basic sanity checks that the Prometheus PushGateway configuration is valid.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Good to see an example of how this is done.
We usually hard wrap at 80 characters, I think some lines go over right now.
I think you should squash these commits.
Enabled bool `long:"enabled" description:"Enable pushing metrics to Prometheus PushGateway"` | ||
Host string `long:"host" description:"Prometheus PushGateway host address"` | ||
Port int `long:"port" description:"Prometheus PushGateway port"` | ||
PushURL string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I think you should add a doc comment to describe PushURL
.
Other metric criteria to collect:
End goal:
Comments:
|
@GeorgeTsagk: review reminder |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Closing this in favor of #737
Equip the test orchestrator with the ability to push metrics on execution time to a configurable remote prometheus push gateway.
Related to: #662 (
loadtest
metrics vs.tapd
metrics)