<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10pt" ><div dir="ltr" >Hey Reid, Ken,<br><br>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.<br><br>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. :)<br><br>Thanks again for your answers.<br> </div>
<div dir="ltr" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div dir="ltr" ><div style="font-size: 12pt; font-weight: bold; font-family: sans-serif; color: #7C7C5F;" >Gerry Sommerville</div>
<div style="font-size: 10pt; font-weight: bold; font-family: sans-serif;" >Db2 Development, pureScale Domain</div>
<div style="font-size: 8pt; font-family: sans-serif; margin-top: 10px;" ><div><span style="font-weight: bold; color: #336699;" >E-mail: </span><a href="mailto:gerry@ca.ibm.com" style="color: #555">gerry@ca.ibm.com</a></div></div></div></div></div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<blockquote data-history-content-modified="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: Ken Gaillot <kgaillot@redhat.com><br>Sent by: "Users" <users-bounces@clusterlabs.org><br>To: Cluster Labs - All topics related to open-source clustering welcomed <users@clusterlabs.org><br>Cc:<br>Subject: [EXTERNAL] Re: [ClusterLabs] Configuring millisecond timestamps in pacemaker.log.<br>Date: Mon, Jan 11, 2021 3:17 PM<br>
<div><font size="2" face="Default Monospace,Courier New,Courier,monospace" >Pacemaker doesn't currently support it, sorry. It should be pretty easy<br>to add though (when built with libqb 2), so hopefully we can get it in<br>2.1.0.<br><br>Of course Pacemaker has always supported logging via syslog, and syslog<br>can be configured to use high-res timestamps, so that's a workaround.<br><br>Does anyone have a strong opinion regarding using high-res timestamps<br>in the Pacemaker detail log whenever supported, vs adding a new<br>sysconfig option for it? I feel like we have a ridiculous number of<br>options already, and the detail log is expected to be verbose.<br><br>On Mon, 2021-01-11 at 19:12 +0000, Gerry R Sommerville wrote:<br>> Hello,<br>><br>> I am wondering if it is possible to configure high resolution<br>> timestamps (including milliseconds) in the pacemaker.log? I was able<br>> to get hi-res timestamps in the corosync.log by adding 'timestamp:<br>> hires' under the logging directive in corosync.conf. I was hoping<br>> Pacemaker has something similar but I don't see anything in<br>> '/etc/sysconfig/pacemaker' or the Pacemaker documentation regarding<br>> hi-res timestamps.<br>> <br>> Gerry Sommerville<br>> Db2 Development, pureScale Domain<br>> E-mail: gerry@ca.ibm.com<br>--<br>Ken Gaillot <kgaillot@redhat.com><br><br>_______________________________________________<br>Manage your subscription:<br><a href="https://lists.clusterlabs.org/mailman/listinfo/users" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a> <br><br>ClusterLabs home: <a href="https://www.clusterlabs.org/" target="_blank">https://www.clusterlabs.org/</a> </font><br> </div></blockquote>
<div dir="ltr" > </div></div><BR>