juju_metrics takes a long time

[Haw Loeung]

Hi,

We're trying to use the metrics from 'juju_metrics' (from juju-introspection) via telegraf and feed that into our prometheus instance. Unfortunately, it seems juju_metrics takes a long time to run. On our shared Juju 2.x controller running 2.4.3:

machine-0: real 0m29.995s
machine-1: real 0m7.402s
machine-2: real 0m44.294s

[Tim Penhey (thumper)]

Getting the metrics should be fast. I have a strong suspicion that this is related to gathering the mongo metrics.

[John A Meinel (jameinel)]

We should consider what Stats we can get quickly and possibly skip some of
them if it takes too long. Certainly it is better to get timely incomplete
stats than no stats. Especially when trying to figure out why things are
slow/overloaded.

John
=:->

On Fri, Nov 2, 2018, 07:25 Tim Penhey <<email address hidden> wrote:

> Getting the metrics should be fast. I have a strong suspicion that this
> is related to gathering the mongo metrics.
>
> ** Changed in: juju
> Milestone: None => 2.5-rc1
>
> ** Changed in: juju
> Status: New => Triaged
>
> ** Changed in: juju
> Importance: Undecided => High
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1800713
>
> Title:
> juju_metrics takes a long time
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1800713/+subscriptions
>

[Tim Penhey (thumper)]

For Juju 2.4.7 and later, the slow part (which happens on big controllers) can be skipped by setting the following:

juju controller-config features=[disable-state-metrics]

[Anastasia (anastasia-macmood)]

Removing from a milestone as this work will not be done in 2.5 series.

[Canonical Juju QA Bot (juju-qa-bot)]

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.