Hi,
On Tue, 16 Aug 2016 12:45:23 +1200
Jason Haar wrote:
> > https://nxlog.co/disappearing-windows-dns-debug-log
>
> So does this mean if you reconfigure to write to a new C: directory (better
> than fiddling with the acls on a default system directory), then all is
> well? That would be great
On Mon, Aug 15, 2016 at 11:22 PM, Botond Botyanszki wrote:
> https://nxlog.co/disappearing-windows-dns-debug-log
>
So does this mean if you reconfigure to write to a new C: directory (better
than fiddling with the acls on a default system directory), then all is
well? That would be great :-)
-
w what you did.
>
> Again, all just FYI.
>
> -Original Message-
> From: Botond Botyanszki [mailto:b...@nxlog.org]
> Sent: Monday, August 15, 2016 2:49 AM
> To: nxlog-ce-users@lists.sourceforge.net
> Subject: Re: [nxlog-ce-users] parsedate not working on Microsoft DNS
> d
YI.
-Original Message-
From: Botond Botyanszki [mailto:b...@nxlog.org]
Sent: Monday, August 15, 2016 2:49 AM
To: nxlog-ce-users@lists.sourceforge.net
Subject: Re: [nxlog-ce-users] parsedate not working on Microsoft DNS debugging
log file
Hi,
On Mon, 15 Aug 2016 13:34:18 +1200
Jason Haar wr
Hi,
On Mon, 15 Aug 2016 13:34:18 +1200
Jason Haar wrote:
> I end up with $origDate="15/08/2016 10:26:18 AM", but no $xxtimestamp - so
> strptime doesn't like the 'ampm' meethinks?
>
> Is there any way to do this is a locale-friendly manner? I guess I could go
> do some grotty math like "if $amp
Hi there
I'm trying to push DNS logs into graylog and it looks like the nxlog
parsedate function doesn't like the time format
eg
15/08/2016 10:26:18 a.m. 0CF8 PACKET 044E6310 UDP Rcv 1.2.3.4
83a8 Q [0001 D NOERROR]
(13)2sf-apdpdx201(2)xx(11)urifblecorp(3)net(0)
So parsedat
