juju metrics reporting can be extremely slow
Bug #1732192 reported by
Junien Fridrick
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Hi,
We just had a load spike on our controller running 2.2.4.
I tried to get metrics from juju (using the introspection proxy from axw), and it took 21 minutes for me to get a reply.
I'm sure that we can do better, even when under high load.
Thanks
tags: | added: canonical-is |
To post a comment you must log in.
I think to be useful, we need to be able to return interesting metrics even if things are under load. If we have some metrics that need DB access, then we should optionally skip them. Better to lose those metrics than lose visibility on the entire system.