NetXMS Support Forum

This works for me:
parents = GetObjectParents($object);

foreach(p : parents)
{
   if (p->type == 5 && p->name == "Something") return true;
}
return false;

Two things to note:
1) it only takes "direct" parents of the node, its not upwards recursive, so doesnt take parents of the node's parents into account
2) CheckTrustedNodes (or equivalent security) will need to be correctly set

You can run the script directly on an object using "Execute server script" to check whats going on.
I suggest adding this into the foreach loop to make debug easier:
println("Type: " . p->type . " Name: " . p->name);

1) use $object variable, not $1
2) yes, its an "NetObj" class object
3) sounds like a bug, log it in bug-tracker

The function you want to use is probably FindDCIByDescription and then GetDCIValue.

Or just use GetDCIValueByDescription

3 more videos added over the last couple of days.
Basics series is now finished and the Advanced series is getting worked on.

As mentioned previously, I am still accepting requests for topics to cover in Advanced, if you guys have any suggestions, let me know.

Yes, its 2 OIDs.
One is traffic received (download), other traffic sent (upload).

You are correct that its a counter of bytes received on an interface since initialization, but that is fine.
This is why we do the transformations I mentioned.

NetXMS will turn those numbers into bits/s.

All NMS's do it like that.

Those 2 are the right OIDs.

In DCI Transformation set:
Delta calc: Average delta per second
In transform script: "return $1 * 8;"

Yes, NetXMS will correctly detect multiple MACs on ports, and will know there is an un-managed switch behind your normal managed switch on port x.

When server first starts, the DCI has no new collected data yet.

Script around it and return an error like so:

tableOld = GetDCIValue($node, dciId);
if (tableOld == null) return 0;


Look into the tomcat logs, is the app properly deployed?

You can also install the web-manager, and deploy the app using it.
It will show you a lot of details and statistics, as well if the app deployed or not.

How are you getting the data - from SNMP or nxagent?

Because the answer depends on what you are using.

You need to handle everything within EPP (Event Processing Policy).

General howto here:
https://wiki.netxms.org/wiki/How_to_send_e-mail_notification_when_disk_space_is_low

Then in the EPP filtering script, you need to filter out depending on the times you require.
You can use these threads as an inspiration:
https://www.netxms.org/forum/configuration/time-schedule-for-e-mail-notification/
https://www.netxms.org/forum/configuration/notification-about-event-only-during-defined-period-of-time/

More info on nxsl (NetXMS Scripting Language):
https://wiki.netxms.org/wiki/Scripting_Guide

More info on the 'time' class within nxsl:
https://wiki.netxms.org/wiki/NXSL:TIME

If you have more questions, either post here, or come visit us in the IRC channel

Quote from: mkemerci on June 10, 2015, 11:46:27 PM
I saw that I can use ServiceResponseTime.HTTP on any agent. But DCI must be under that agent's node. I could not use netsvc. response time yet.

Is it possible to create the ServiceResponseTime.HTTP DCI on service's node and check it with an other node (same  as network service functionality) ? Or is there any other way to do this ?
thanks.

Create the DCI for the node, and then set the proxy node as the node from which the agent should execute the query.

Why not just handle all of this in EPP with nxsl scripts?
You can filter based on time and create really complex rules to fire emails/sms's, etc.

There are already some examples on the forums and the wiki.

The auto apply rules are called for a node each time a configuration poll happens on that node.
You can simply "return true;" and "return false;" in the first config poll run, the next run will then pick it up correctly.

I would advise against binding based on a DCI result, it will produce random results (like you are describing and more).
Instead create a snmp transport from the actual auto-apply script, and get actual value from there, and do your decisions based on that.

Start the server with 'netxmsd -d' command to run as a deamon.

Then use 'nxadm -i' to connect the shell to the server.
You can then kill / reattach the shell as much as you want without influencing the server process.