when reporting speed, magpie should provide some kind of statistics instead of realtime speed
Bug #1948976 reported by
Garrett Neugent
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-magpie |
New
|
Undecided
|
Unassigned | ||
Bug Description
when checking the speed via juju status, magpie will currently show the most recent speed check for a given machine, when it would be more helpful to instead include some kind of statistical analysis. I think as a first attempt, max/min/average would be helpful, to help identify but account for outliers.
Revision history for this message
| Andrea Ieri (aieri) wrote | #1 |
| tags: | added: bseng-15 |
Revision history for this message
| Billy Olsen (billy-olsen) wrote | #2 |
To post a comment you must log in.
Our use case is basically having magpie identify:
* a baseline of best-case-scenario networking performance
* outliers, which can be a symptom of a misconfiguration
Having the current speed in the juju status output is not wrong, but at the moment the only way to provide the above is having a human visually watch the juju status output.
I think a 'report' action showing min/max/avg as Garrett mentioned would make reviewing a cloud a lot easier.