I now have quite a few servers I want to monitor for "Node Down", but don't want to just allow everything or i'd get too many alerts as Network Discovery is enabled. In the IF Condition, the order of the objects seems to be in an odd order (see picture). It doesn't seem to be the order I added them to NetXMS either. Would it be possible to allow the list to be in Alphabetical order, so it's easier to see if an object has been missed out? Thanks, Chris [image: 2021-10-10_20-31.png]

Did you manage to simulate the problem or is it OK for you? Thank you @dawid-kellerman said in Windows EventLog - wineventsync.nsm - how to set additional sending: Hi Hugo I do not know if this relates to the wineventsync but I think it does..  For Windows Event Log agent keeps status information in Windows registry. On agent start records that were added while the agent was stopped will be parsed. From https://www.netxms.org/documentation/adminguide/log-monitoring.html?highlight=registry I will also test to see Regards Dawid

+1

More to the point, the Debian packages ship with a config file that says mysql.ddr.

Hi, it depends on resources available. Developer that was working on it left the company, and currently we do not have any iOS developer onboard (and they are quite expensive as well). Ultimate goal is to have iOS client though. Best regards, Victor

Hi, really nice idea actually, and should be fairly easy to implement. Added to my TODO list Best regards, Victor

Hello Would it be possible to implement time frame selection in node-performance tab, but one that changes all metric displays at once? Egert

I think it would be helpful to have a script generator that would allow a visual gui in building custom scripts that could be used with netxms or maybe provide a repository for people to post there custom scripts that maybe helpful for others.

Yes, server console is not available in web UI, because widget that we use for terminal emulation only exist as desktop version. Best regards, Victor

It would be great if there was a facility to allow you to debug on just one node or maybe just one DCI.  If we are looking for something and turn up the debug level (say 6 for example) it generates about 4K+ lines per second!  Not really useful to get information on a specific issue.

Hi, We are implementing Jira (Cloud Version) and looking to integrate with NetXMS.  It would be great if you had Jira integration for the Cloud version.  I can make it work as-is. I have determined to use NetXMS Action to create issue via Jira Rest API, and create Alarm comment with JiraIssue={issueKey}.  Using Jira Webhooks, update NetXMS on issue status change (I have extended WebAPI to support updates via a GraphQL API).  Jira would Acknowledge Alarm when assigned and add Alarm comment with user assigned JiraUserAssigned={jiraUserName}.  On Jira issue close, Resolve Alarm and add comment as needed.  Then as routine maintenance, terminate resolved alarms using scripting.  It would be helpful to have update access to the NetXMS alarm helpdeskReference field using similar session methods such as session.updateAlarm(Alarm alarm) or session.linkHelpdeskIssue(long alarmId, string helpdeskReference). Is there any visual indication in NetXMS Alarm browser for helpdesk linked alarms? Thanks.

OK, I rescind the not working I had just not ever saw the option under the "Other options" section which I am guessing was added.  Changing it on the Last Values for me still changes ALL of them to either using multipliers or not.  Thanks for pointing this out!

This has been implemented in developers version and will be released soon.

Terminated alarms are kept in alarm log and cleaned by housekeeper (by default after 90 days, this period can be changed). You can access them via "Alarm Log" view or directly in database. Best regards, Victor

Hi, just added severity filter option to wineventsync subagent. Now for every reader you can specify SeverityFilter parameter, which is either bit mask  or severity level names separated by commas. Below are level names and their values: Critical = 0x100 Error = 0x001 Warning = 0x002 Information = 0x004 AuditSuccess = 0x008 AuditFailure = 0x010 To accept only warning and error events: SeverityFilter = 0x012 or SeverityFilter = Warning,Error This change will be included into next patch release. Best regards, Victor

It would be nice if you could expand the size of the Edit Script window anywhere it shows up.  Currently, the pain point is in the Edit Threshold section of the application, but if there are other areas it would probably be helpful as well.  If you have any significant amount of code it is difficult to write within the small window which only allows about 50 characters before scrolling.

Thanks for the reply. Is there any reference in database for example when node went down/up ? Maybe i could extract it with another app and build statistics and link it back with tool menu. Currently one way i can think of is to parse event logs and look for specific events. For example node would have tool lets call it uptime and it would show latest x amount of downtimes and durations and then more general uptime info for month/year etc.

The System.Services agent table is great!  Even better would be to add Configured "logon as" or "run as" account. Startup type "auto (delayed start)" Thanks.

Thanks Victor!

Hi, I've added feature request for option to display ICMP stats on map - https://track.radensolutions.com/issue/NX-2007. For placing data on the link you can right-click on link, go to properties, data sources, and add one or more DCIs whose value should be displayed on the link. Best regards, Victor