"Problem reporting" section of tech spec rather loose

[Adam Williamson]

On Mon, 2014-06-09 at 14:21 +0200, Miloslav Trmač wrote:
> 2014-06-07 0:38 GMT+02:00 Adam Williamson <awilliam at redhat.com>:
> 
> > "Problem reporting
> >
> > Problems and error conditions (e.g. kernel oopses, Selinux AVCs,
> > application crashes, OOM, disk errors) should all be reported in the
> > systemd journal.
> >
> > Support for sending this information to a central place (like abrt does
> > for crashes today) is mandatory."
> >
> > the word "must" appears multiple other times in the page, so we have the
> > old chestnut of whether we're using "must" and "should" with strict
> > definitions, or as synonyms, or what. And then the second paragraph
> > throws in another candidate: "Support...is mandatory". What exactly is
> > "is mandatory" supposed to mean in this context?
> 
> 
> IIRC this is different from the status quo mainly for *roles*: i.e. even if
> the upstream daemon defaults to logging to its own private log files, the
> role is expected to configure the daemon to log to journal/syslog instead
> (or perhaps in addition).  This would in turn make it possible for a single
> “forward logs to $host” configuration to apply to all roles.

Other tech spec items explicitly indicate when they're scoped to roles,
so if that's intended here, it should probably be added.

> 
> > "kernel oopses, Selinux AVCs, application crashes, OOM, disk errors"
> >
> I think all of these end up in the journal/syslog already (except may be
> the crashes, where kernel writing anything to dmesg is IIRC arch-specific).

They wind up in the journal, yes - but it's the 'support for sending
them to a central place' bit that's missing.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net