We recorded some thoughts on logging at the quartz sprint

[William Reade]

I'm not sure we should be sending any logging on stdout -- isn't that for
*results*, for consumption by other machines?

On Tue, Jun 28, 2016 at 11:52 AM, Reed O'Brien <reed.obrien at canonical.com>
wrote:

> Relevant to the conversation currently happening at the core sprint, we
> recorded some thoughts on what to log at what level, when and where.
> Thoughts and examples appreciated.
>
>
> +-------+-----------+-----------------------------------+---------+------------+
> | Level | Audience  | Purpose                           | Example | I/O
> Stream |
>
> +-------+-----------+-----------------------------------+---------+------------+
> | ERROR | End User  | Conveys information that requires |         |
>      |
> |       |           | immediate action. Triggers call   |         |
> STDERR   |
> |       |           | tree/pager duty.                  |         |
>      |
>
> +-------+-----------+-----------------------------------+---------+------------+
> | WARN  | End User  | Conveys information that requires |         |
>      |
> |       |           | user intervention soon to ensure  |         |
> STDERR   |
> |       |           | continuos smooth operation.       |         |
>      |
>
> +-------+-----------+-----------------------------------+---------+------------+
> | INFO  | End User  | Conveys contextual "happy path"   |         |
>      |
> |       |           | information about startup.        |         |
> STDOUT   |
>
> +-------+-----------+-----------------------------------+---------+------------+
> | DEBUG | Developer | Conveys detailed function level   |         |
>      |
> |       |           | information to aid in isolating   |         |
> STDOUT   |
> |       |           | code paths during devleopement.   |         |
>      |
>
> +-------+-----------+-----------------------------------+---------+------------+
> | TRACE | Developer | Conveys detailed branch level     |         |
>      |
> |       |           | information to aid in isolating   |         |
> STDOUT   |
> |       |           | code paths during development.    |         |
>      |
>
> +-------+-----------+-----------------------------------+---------+------------+
>
> --
> Reed O'Brien
> ✉ reed.obrien at canonical.com
> ✆ 415-562-6797
>
> --
> 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/20160628/da34a613/attachment-0001.html>