[CI][RFE] implement statsd "ping" within CI runs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
Medium
|
Unassigned |
Bug Description
Hello there!
While squashing timeouts issues within the CI, I thought it would be really, really good to have some fine-grained data about time.
An easy way to do so is to add a statsd[1] daemon that will feed grafana with tagged "pings", allowing to display timelines with extended data.
For instance, we might, before and after each CI step, send a "ping" to the statsd stating "start provisioning", "finished provisioning", "starting container-prepare", .... "starting tempest" and so on.
We might even get deeper, and implement those "ping" directly within tripleoclient, tripleo-
I know some of the metrics returned by ansible are already used, but statsd being "made for it", implementing such a service would really be nice, since we will be able to pin-point what takes longer than usual, compare timelines and so on.
Support might even be easier if we get those new, precise metrics.
What do you think?
Cheers,
C.
[1] https:/
Some more info: https:/
description: | updated |
summary: |
- [CI] implement statsd "ping" within CI runs + [CI][RFE] implement statsd "ping" within CI runs |
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |