On Tue, Nov 29, 2016 at 5:26 PM John Meinel <j...@arbash-meinel.com> wrote:
> Thanks for charming this up. It does feel like if this is useful we should
> just be exposing it via an authenticated endpoint. I realize we don't run
> an HTTP server on all agents, but certainly it feels like it should be
> exposed for the controllers.
Agreed. I'm thinking we'll end up with an exporter (introspection proxy)
for machine/unit agents, and have the controllers expose metrics directly
over the API server.
> On Nov 29, 2016 7:32 AM, "Andrew Wilkins" <andrew.wilk...@canonical.com>
> Hi folks,
> Just a quick note to let you know about an application and charm I wrote
> recently to make it easier to introspect Juju controllers/agents.
> $ juju deploy ~axwalk/juju-introspection --to <machine>
> $ juju expose juju-introspection
> This will deploy https://github.com/axw/juju-introspection-proxy, which
> serves the introspection endpoint of each agent on the same machine over
> HTTP via the port 19090 (configurable using "port" application config).
> For example, say you deploy it to machine 0, and that machine also has the
> unit mysql/0. You can access each agent's introspection endpoints via:
> You can also hit "/agents", and get a list of agents on the machine.
> Juju 2.1 will have Prometheus instrumentation, and you'll be able to
> access the metrics via:
> The juju-introspection application is relatable to
> I'll send another email later with more details about the monitoring side
> of things, but just wanted to make sure people are aware of this now, to
> aide their debugging efforts.
> Juju-dev mailing list
> Modify settings or unsubscribe at:
Juju-dev mailing list
Modify settings or unsubscribe at: