Hi,
On Sun, 30 Jun 2013 17:25:34 +
Marvin Nipper wrote:
> I had actually looked at that. I'm probably just being dense, but what
> is not obvious in their examples is how one would use that in a
> "compound" scenario, which is how most folks want to capture Windows
> logs, e.g. rarely w
> (that enables/disables the entire, multi-line structure). You could
> obviously also code everything on one (really long) line, but it then becomes
> impossible to re
ad, and even more difficult to modify.
>
>
> Anyway... THANKS again for the weekend reply. It allowed me to try s
omes
> impossible to re
ad, and even more difficult to modify.
>
>
> Anyway... THANKS again for the weekend reply. It allowed me to try some new
> things, and sort out my previous issue. THANKS for your time and help.
>
> -Original Message-
> From: Botond Botyanszki [
s issue. THANKS for your time and help.
-Original Message-
From: Botond Botyanszki [mailto:b...@nxlog.org]
Sent: Sunday, June 30, 2013 2:00 AM
To: nxlog-ce-users@lists.sourceforge.net
Subject: Re: [nxlog-ce-users] im_msvistalog Channel Query issue
Marvin,
The query below works ok for me
Marvin,
The query below works ok for me on a W2K8R2.
Try setting Loglevel to Debug and check what query nxlog gets actually,
look for "msvistalog query xml" in nxlog.log
The query is passed to the windows eventlog API as is, nxlog does not deal
with it in any way.
For invalid channels the subscri
