juju metrics reporting can be extremely slow

Bug #1732192 reported by Junien F
18
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

Junien F (axino)
tags: added: canonical-is
Revision history for this message
John A Meinel (jameinel) wrote :

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.

Changed in juju:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: High → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.