On 7 May 2015 at 00:58, Charles Butler <[email protected]> wrote:
> > On Wed, May 6, 2015 at 3:53 AM, Stuart Bishop <[email protected] > > wrote: > >> My own use case would be to make a more readable debug-logs, rather >> than attempting to parse the debug-logs output ;) Hmm... I may be able >> to do this already via the Juju API. >> > > Personally - i feel like this is a *great* use case for an opengrok filter > w/ logstash. Translate that structured data into something meaningful in > elasticsearch and search/aggregate/tail like a champ. > Agreed - that would be awesome. When we get to this we should aim to have Juju emit structured log data that could be used to feed things like logstash. If we do it right then hopefully grok won't be needed because the log data will already be structured. No promises about when this might happen though. At least the logging work currently being done provides a good basis to add logging to external systems.
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
