NetXMS Forum

Thank you, I will try to get a better understanding of that counter.  On one of our servers, we are seeing regular valures around 200 - 250 for that paramater and spikes over 600. Thanks again, Kevin

Yes that file exists in the C:\netxms\bin directory.

I just experimented with using process.io.xxx with a transformation of "Average delta per second", and I compared it to the: Counter = UserProcess.SQLServer.IO.xxx:"\Process(sqlservr)\IO xxx Bytes/sec":60:A:INT:"Average I/O xxx Bytes for sqlservr.exe over past minute" Both graphs are virtually identical. I thought this might be helpful if anyone is reading this thread. Kevin

I would like to be able to create custom agent configuration settings and save them with a template.  Then if a device is a memeber of that template, it would automatically add those custom agent configuration settings to all nodes of that template. For example, if I create a SQL server template, I would like to store the following custom agent counters with the template.  Then anytime I add a new device to that template these custom agent counters will automatically get installed: *WinPerf Counter = UserProcess.SQLServer.CPU:"\Process(sqlservr)\% Processor Time":60:A:INT:Average % CPU Time for sqlservr.exe over past minute Counter = UserProcess.SQLServer.IO.ReadBytes:"\Process(sqlservr)\IO Read Bytes/sec":60:A:INT:Average I/O Read Bytes for sqlservr.exe over past minute Counter = UserProcess.SQLServer.IO.WriteBytes:"\Process(sqlservr)\IO Write Bytes/sec":60:A:INT:Average I/O Write Bytes for sqlservr.exe over past minute Counter = UserProcess.SQLServer.IO.OtherBytes:"\Process(sqlservr)\IO Other Bytes/sec":60:A:INT:Average I/O Other Bytes for sqlservr.exe over past minute Counter = UserProcess.SQLServer.Memory:"Process(sqlservr)\Working Set":60:A:INT:Average Memory usage for sqlservr.exe over past minute

Thank you, I am starting to feel really dumb for all my little typo's.  It is working great. Thanks again, Kevin

For process counters in question, if process does not exist, counter will return 0. But in general, if you try to add non-existing performance counter, it may fail on agent startup, or may return error to data collection requests - depending on what PDH returns to agent. Best regards, Victor

Yes you may publish it.  Thank you for asking and I am glad I can help.

Currently, the only thing you can easily monitor is interface up/down. System detect all interface state changes and send predefined events: SYS_IF_DOWN and SYS_IF_UP. You can filter and process these events in event processing policy, so you will need to configure only a few rules in EPP. For other things, there are some work to do Best regards, Victor

Implemented in 0.2.20. This feature is disabled by default, to enable it you should set server configuration variable SyncNodeNamesWithDNS to 1. Best regards, Victor

Thank you the corrected MIB file worked perfectly. Kevin

@kghammond said in Changing the name of switch ports: Any rough idea when you may finish the next release? It should be very soon. Actually, I have plans to release it in January, but I have stuck on one required functionality (advanced event correlation), so release was postponed. The good side of it is that I will be able to include additional minor features like this. Best regards, Victor

Hello! It will be possible in upcoming version 0.2.20. Currently, you can run discovery with one community, accepting only devices with SNMP support (to avoid adding devices with different community with incorrect settings), then change the community and wait for next discovery cycle. Best regards, Victor