NetXMS Support Forum

Im using this metric (deployed by a template attached to all Windows systems):
ExternalMetric = MSSQL.InstalledInstancesCount:powershell -NonInteractive -NoProfile -Command "& { (Get-ItemProperty \"HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\").InstalledInstances.Count }"

Then you can use something like this in automatic bind/auto apply:
value = $node.readAgentParameter("MSSQL.InstalledInstancesCount");
return (value != NULL && typeof(value) == "int32" && value > 0);


Oh nice, thank you. Maybe you can add this to the manual for future reference!

Thank you, I did not know about this parameter! I will report back.

We have some issues with ExternalMetricProvider:
As some scripts need more time to run for collecting data, we query them by ExternalMetricProvider instead of ExternalMetric. This works ok, but these metrics switch to "Unsupported" from time to time, if the server queries the metric immediently after a system restart and the scripts from ExternalMetricProvider have not yet finished after NetXMS agent start. If script has finished the first time after agent startup, the metrics can be pulled without error and it works fine. 

Is there a workaround to prevent this issue? I tried to switch the DCI to "Cached mode", but it looks like this does not make any difference.

Are you sure about that there is no concept for DCI summary tables from table DCI? I am talking about this.
In the meantime I wrote a script to query each DCI one by one and join the results to one table (the same way the summary table for table DCI works), so you can consider my question as answered.

Thank you, I am working with the API already. I am asking about creating an ad-hoc summary table from a table DCI. I suspect this is not yet implemented.

Is it possible to use the Web API for requesting an adhoc summary table for a Table DCI?
https://netxms.org/documentation/adminguide/rest-api.html#adhoc-summary-table

If yes, how?
If no, what is the best way to export multiple Table DCI values to a CSV file automatically (meaning, by script)?

I can confirm, this metric transform script crashes the server process:
time = DateTime(253402297200);
return time.format("%d.%m.%Y");

I'm not so good at crash dump analysis but I tried it anyway. It look like the server crashes while NXSL tries to process an invalid timestamp?

I experienced some server crashes recently with version 5.1.3 on Windows. At the moment the server is up and running, but can you take a look at the crash dump?
I suspected it has something to do with user support notifications, as we started using them the day before the crashed started.

Thank you, I will experiment with that!

I realized that there is Python-subagent for scripting, but I can't find any examples how to use it or any documentation. Unfortunately I don't know much Python but I'm happy to learn.

Victor, thank you very much! I should have realized this myself...

Im talking about this:
#ifdef _WIN32
// Include our own wrapper header on Windows to avoid conflict with MySQL client library
#include <mariadb.h>
#elseI see mysql.h included MariaDB library, but not mariadb.h?

I saw a method "[correlateTo(eventId) ⇒ void" for events in the NXSL documentation.
Can I use this method in the Event Processing Policy to correlate events "manually" ? I can imagine a few scenarios for which this would be very useful.
Thanks in advance.