NetXMS Support Forum

I created a script in the Script Library names ThreeCXServiceFilter (I changed from == "Auto" to like "Auto*" because some are "Auto (Delayed)")

services = $node->readAgentTable("System.Services");
if (services == null)
   return null;

instances = %();
for(r : services->rows)
{
   name = r->get(0);
   startup = r->get(4);
   if (name like "3CX*" and startup like "Auto*")
      instances->append(name);
}

return instances;

In my template I added a Data Collection Configuration. See the screenshots for that configuration.

Let me know if you need anything else.

I have not set it up, but I can get you the link for the latest version (I could find):

https://netxms.org/download/releases/3.7/netxms-reporting-server-3.7.116.zip

I asked for clarification on the agent upgrades here

https://www.netxms.org/forum/announcements/netxms-3-9-version-3-9-298/msg30609/#msg30609

You will need to update the agent with some other package manager/manually. Going forward, agent upgrades should work as intended.

OK, thank you for getting that fixed and for the extra details.

I pushed out 3.9.298 using an alternate method. I was then able to use NetXMS Package Manager to essentially reinstall 3.9.298 without errors. I will take that as a good sign.

Hey, yeah, that makes more sense.

I don't think there is a way to save log filters and I couldn't figure out any other work around/option.

The closest I can see would be to use the Grafana integration
https://www.netxms.org/documentation/adminguide/grafana-integration.html
or setup the reporting server
https://www.netxms.org/documentation/adminguide/reporting.html

I have not used either of those so I don't know the difficulty of getting them setup. It might be more work than it's worth.

- Fixed bug in centralized agent upgrade on Windows

Does that mean once server and agent are on 3.9.298, future centralized agent upgrades should work? Or should it work with just server on 3.9.298?

I am trying to upgrade Windows agents 3.9.280 from Linux server 3.9.298 and get the "Agent's version doesn't match..." error message.

To save it the event listing, you can use the export to csv button in the upper right or use the shortcut key Crtl-Alt-X.

I am running 3.8.382. I just tested the script as written in this post and it finished successfully. So I do not think it is a bug.

Can you post your script and any error messages?

Gary

Works perfectly. Thank you!!

I am trying to write a discovery filter script for Windows services that start with a common name and are set to auto startup. I have experimented with different things all day with no luck.

Here is what I thought would work, but it does not

name = $1->get(0);
startup =  $1->get(4);
if (name like "3CX*" && startup == "Auto")
{
return true;
}
return false;

I was hoping $1 would return a row but seems it does not.

In the manual it says values are returned with ~~~ between them, but I am not sure how to read those in the script.

Any assistance would be appreciated.

Gary

Thank you for the detailed response. This is exactly what I needed.

Is there any available information regarding "Windows event log synchronization, server side parsing and agent side filtering" from the 3.6 release notes? It sounds like it is different than the Parser Definition file.

When looking at the Alarm Browser, Summary Tables, and probably others, you can right click and choose Object Details. It would be helpful if the Object was selected in the Objects tree to easily identify which customer Container the Object is located.

https://www.netxms.org/forum/installation/agent-lost-contact/msg23736/#msg23736

I do not see a way to export that list from the console.

This entry may help to accomplish the export.

https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations#Export_list_of_interfaces_to_CSV_file