I believe this is supposed to be analogy, not implementation on the i/o stream front.
On 28 June 2016 at 12:09, William Reade <[email protected]> wrote: > 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 <[email protected]> > 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 >> ✉ [email protected] >> ✆ 415-562-6797 >> >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
