juju-introspection-proxy

[John Meinel]

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.

John
=:->

On Nov 29, 2016 7:32 AM, "Andrew Wilkins" <andrew.wilkins at canonical.com>
wrote:

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:
    http://machine-0-address:19090/agents/machine-0/depengine/
    http://machine-0-address:19090/agents/machine-0/debug/pprof/profile
    http://machine-0-address:19090/agents/unit-mysql-0/depengine/
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:
    http://machine-0-address:19090/agents/machine-0/metrics
The juju-introspection application is relatable to ~prometheus-charmers/
prometheus.

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.

Cheers,
Andrew

--
Juju-dev mailing list
Juju-dev at lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/
mailman/listinfo/juju-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20161129/fe69d9ce/attachment-0001.html>