EventLogs not shipped from Windows 2016 to NXlog

This support forum board is for support questions relating to Nagios Log Server, our solution for managing and monitoring critical log data.
Locked
dlukinski
Posts: 1130
Joined: Tue Oct 06, 2015 9:42 am

EventLogs not shipped from Windows 2016 to NXlog

Post by dlukinski »

Hello Nagios Log Support

We've configured NXlog client on Windows 2016, but no logs shipped to Nagios Log

Conf file attached.
You do not have the required permissions to view the files attached to this post.
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: EventLogs not shipped from Windows 2016 to NXlog

Post by cdienger »

If your goal is to only send those specific event IDs you want to use the logical AND and not the OR:

Exec if not ($EventID == 4624 AND $EventID == 4634 AND $EventID == 4648 AND $EventID == 4672) drop();
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
dlukinski
Posts: 1130
Joined: Tue Oct 06, 2015 9:42 am

Re: EventLogs not shipped from Windows 2016 to NXlog

Post by dlukinski »

cdienger wrote:If your goal is to only send those specific event IDs you want to use the logical AND and not the OR:

Exec if not ($EventID == 4624 AND $EventID == 4634 AND $EventID == 4648 AND $EventID == 4672) drop();
I am not getting ANY logs through
- all other LOG shpping installs for Events use OR (AND means combined?)
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: EventLogs not shipped from Windows 2016 to NXlog

Post by cdienger »

Not getting ANY logs would make sense with this logic. For example, say event 4624 came in, the first part:

$EventID == 4624

would evaluate to true, but the rest of the line would still be executed:

$EventID == 4634

would evaluate to false because 4624 !=4634. The action would then be to drop();
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
dlukinski
Posts: 1130
Joined: Tue Oct 06, 2015 9:42 am

Re: EventLogs not shipped from Windows 2016 to NXlog

Post by dlukinski »

cdienger wrote:Not getting ANY logs would make sense with this logic. For example, say event 4624 came in, the first part:

$EventID == 4624

would evaluate to true, but the rest of the line would still be executed:

$EventID == 4634

would evaluate to false because 4624 !=4634. The action would then be to drop();
Log shipping still not happenning (changed CONF file even so that all other CONF files we had successfully worked with "OR" instead)
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: EventLogs not shipped from Windows 2016 to NXlog

Post by scottwilkerson »

Can you share the current config for us to review?
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: EventLogs not shipped from Windows 2016 to NXlog

Post by cdienger »

I see you've opened a ticket. We'll close this thread and continue to work through the ticket.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked