Why not stick to the UNIX principle and compose a pipeline? With https://bugs.launchpad.net/juju-core/+bug/1390585 fixed it could be as simple as "juju debug-log --no-stream --replay | pastebinit"
On 4 March 2015 at 13:45, Jorge O. Castro <[email protected]> wrote: > Hi everyone, > > Sometimes people deploy things like a complex bundle on a cloud and it > doesn't work. Having to wrangle the person to find out which units > broke, juju sshing in and manually digging around logs and refiring > off hooks, etc. is time consuming. > > Marco and I thought something like `juju pastebinit` would be a good > idea. Just give me a dump of all the logs on the units so I can send > that to the bundle/charm author. > > https://github.com/juju/plugins/issues/52 > > The eco team is gearing up for a sprint so our pattern is kind of > full, so I'd thought I'd send this out to the list to see if anyone is > looking for a quick plugin to bust out that would help people out in > the field debug their problems faster. > > -- > Jorge Castro > Canonical Ltd. > http://juju.ubuntu.com/ - Automate your Cloud Infrastructure > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
