Hello Nagios Log Support
We've configured NXlog client on Windows 2016, but no logs shipped to Nagios Log
Conf file attached.
EventLogs not shipped from Windows 2016 to NXlog
EventLogs not shipped from Windows 2016 to NXlog
You do not have the required permissions to view the files attached to this post.
Re: EventLogs not shipped from Windows 2016 to NXlog
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();
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.
Re: EventLogs not shipped from Windows 2016 to NXlog
I am not getting ANY logs throughcdienger 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();
- all other LOG shpping installs for Events use OR (AND means combined?)
Re: EventLogs not shipped from Windows 2016 to NXlog
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();
$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.
Re: EventLogs not shipped from Windows 2016 to NXlog
Log shipping still not happenning (changed CONF file even so that all other CONF files we had successfully worked with "OR" instead)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();
-
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
Can you share the current config for us to review?
Re: EventLogs not shipped from Windows 2016 to NXlog
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.