Hey Reid, Ken,
Thank you for your quick replies. I figured this was the case. As Ken suggested I will likely work around this by configuring high resolution timestamps in the system log, and I think I can use some journalctl options on systems that don't have rsyslog by default.
I assume that the detailed log is the pacemaker.log which defaults to /var/log/pacemaker/pacemaker.log, my vote would be that this log defaults to high resolution timestamps when possible in the future. :)
Thanks again for your answers.
Thank you for your quick replies. I figured this was the case. As Ken suggested I will likely work around this by configuring high resolution timestamps in the system log, and I think I can use some journalctl options on systems that don't have rsyslog by default.
I assume that the detailed log is the pacemaker.log which defaults to /var/log/pacemaker/pacemaker.log, my vote would be that this log defaults to high resolution timestamps when possible in the future. :)
Thanks again for your answers.
----- Original message -----
From: Ken Gaillot <[email protected]>
Sent by: "Users" <[email protected]>
To: Cluster Labs - All topics related to open-source clustering welcomed <[email protected]>
Cc:
Subject: [EXTERNAL] Re: [ClusterLabs] Configuring millisecond timestamps in pacemaker.log.
Date: Mon, Jan 11, 2021 3:17 PM
Pacemaker doesn't currently support it, sorry. It should be pretty easy
to add though (when built with libqb 2), so hopefully we can get it in
2.1.0.
Of course Pacemaker has always supported logging via syslog, and syslog
can be configured to use high-res timestamps, so that's a workaround.
Does anyone have a strong opinion regarding using high-res timestamps
in the Pacemaker detail log whenever supported, vs adding a new
sysconfig option for it? I feel like we have a ridiculous number of
options already, and the detail log is expected to be verbose.
On Mon, 2021-01-11 at 19:12 +0000, Gerry R Sommerville wrote:
> Hello,
>
> I am wondering if it is possible to configure high resolution
> timestamps (including milliseconds) in the pacemaker.log? I was able
> to get hi-res timestamps in the corosync.log by adding 'timestamp:
> hires' under the logging directive in corosync.conf. I was hoping
> Pacemaker has something similar but I don't see anything in
> '/etc/sysconfig/pacemaker' or the Pacemaker documentation regarding
> hi-res timestamps.
>
> Gerry Sommerville
> Db2 Development, pureScale Domain
> E-mail: [email protected]
--
Ken Gaillot <[email protected]>
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
