[ClusterLabs] Antw: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

[Ken Gaillot]

On Thu, 2018-01-11 at 09:07 +0100, Ulrich Windl wrote:
> Hi!
> 
> More than the location of the log file, I'm interested in the
> contents of the log file: The log file should have a formal syntax
> for automated parsing, and it should be as compact as possible.
> Considering lines like:
> Jan 07 10:07:41 [10691] h01    pengine:     info:
> determine_online_status_fencing:         Node h01 is active
> there are too many repeating blanks in that. Also the order may not
> be optimal: Why not have the priority ("Info:") first after the host
> name? The function name "determine_online_status_fencing" wouldn't
> loose much information if just being called "fencing_status", too
> (IMHO). That would move the most important information that come last
> ("Node h01 is active") toward a common line limit (which is not 160,
> BTW ;-)).
> 
> Regards,
> Ulrich

Well that is the "detail" log :)

Since pacemaker by default also logs to syslog, you can use existing
syslog daemon functionality to save those logs as json, SQL, or
whatnot.

> > > > Ken Gaillot <kgaillot at redhat.com> schrieb am 10.01.2018 um
> > > > 23:34 in Nachricht
> 
> <1515623653.4815.23.camel at redhat.com>:
> > Starting with Pacemaker 2.0.0, the Pacemaker detail log will be
> > kept by
> > default in /var/log/pacemaker/pacemaker.log (rather than
> > /var/log/pacemaker.log). This will keep /var/log cleaner.
> > 
> > Pacemaker will still prefer any log file specified in
> > corosync.conf.
> > 
> > The initial proposal, after discussion at last year's summit, was
> > to
> > use /var/log/cluster/pacemaker.log instead. That turned out to be
> > slightly 
> > problematic: it broke some regression tests in a way that wasn't
> > easily 
> > fixable, and more significantly, it raises the question of what
> > package 
> > should own /var/log/cluster (which different distributions might
> > want to 
> > answer differently).
> > 
> > So instead, the default log locations can be overridden when
> > building
> > pacemaker. The ./configure script now has these two options:
> > 
> > --with-logdir
> > Where to keep pacemaker.log (default /var/log/pacemaker)
> > 
> > --with-bundledir
> > Where to keep bundle logs (default /var/log/pacemaker/bundles,
> > which
> > hasn't changed)
> > 
> > Thus, if a packager wants to preserve the 1.1 locations, they can
> > use:
> > 
> > ./configure --with-logdir=/var/log
> > 
> > And if a packager wants to use /var/log/cluster as originally
> > planned,
> > they can use:
> > 
> > ./configure --with-logdir=/var/log/cluster --with-
> > bundledir=/var/log/cluster/bundles
> > 
> > and ensure that pacemaker depends on whatever package owns
> > /var/log/cluster.
> > -- 
> > Ken Gaillot <kgaillot at redhat.com>
> > 
> > _______________________________________________
> > Users mailing list: Users at clusterlabs.org 
> > http://lists.clusterlabs.org/mailman/listinfo/users 
> > 
> > Project Home: http://www.clusterlabs.org 
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratc
> > h.pdf 
> > Bugs: http://bugs.clusterlabs.org
> 
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.
> pdf
> Bugs: http://bugs.clusterlabs.org
-- 
Ken Gaillot <kgaillot at redhat.com>