NetXMS Support Forum

Right click into the graph -> Presets -> choose what time period you want the graph to show.

Insert into transformation script

return ($1 * 10);

What do the DCI templates contain?

Do you have any complex transform scripts?

Hey guys,

I have written a Puppet module for NetXMS. Sharing it in case someone finds a use for it.
Please note this module is still fairly basic, and I tested in only on Ubuntu Server 12.04.

UPDATE:
The module and its documentation have been moved to GitHub:
https://github.com/tomaskir/netxms-puppet

If you find any issues with this module, or have any feedback, please let me know!

Regards,

tom

With todays update:
Added support for NXSL function calltips in Notepad++.

If anyone gets a chance to try this, let me know if it works

Hi,

Is there any way to return "Unsupported" from a script DCI?

For example, if a SNMPGet fails inside of a script, it would be nice to be able to return "Unsupported" to the DCI, so a proper Alarm can fire.

Thanks!

Quote from: Dani@M3T on October 20, 2014, 05:11:52 PM
I see this feature is in V1.2.17. But how we can use it. I didn't found a documentation.

DCI > Options > Other Options > Use this DCI for node status calculation

What exactly does it do, I dont know

How does status calculation work if this is checked? Can it be checked for multiple DCIs? Etc...

Quote from: Haari on October 20, 2014, 02:07:34 PM
Hello,

tried to do the same Thing like zsing82 but i'm always getting an error:

Status of DCI 98 (NetXMS Agent: Net.Interface.BytesIn64()) changed to UNSUPPORTED

It seems that there is something wrong with the "instance". the filtering script is exactly the one from victors post.

I tried something similar with my hdd's and "FileSystem.MountPoints" as Instance List. This list works and delivers me all the wanted Information. But for the Network Interfaces i end up with this "unsupported"-error.

Any ideas?

Kind Regards
Haari

Attach a screenshot of how your DCI is configured please.

Thank you for sharing

Setup a template item which creates interface DCIs based on instance discovery.
This will do all you need it to do.

We have it setup so that one template DCI item creates DCIs for all interfaces on all our devices dynamically using instance-discovery.
This applies the delta calculation and everything else.

Walk .1.3.6.1.2.1.25.2.3.1 that is the StorageEntry MIB.
Specifically .1.3.6.1.2.1.25.2.3.1.3 will give you the descriptions.

You can only monitor file systems, not separate files, so if you want to monitor a directory, it has to be mounted (the actual directory needs to be mounted), not just a part of a mounted FS.

I have this solved like this: I have a Container in "Infrastructure Services" named "!Unassigned". This Container has an autobind script:

parents = GetNodeParents($node);

foreach(p : parents)
{
if ((p->type != 1) && (p->name != "!Unassigned"))
{
return false;
}
}

return true;


Please note you have to have "CheckTrustedNodes" set to 0 for this script to work.

For a further explanation of what this script does, see this thread:
https://www.netxms.org/forum/general-support/bound-unbound-nodes/

I believe that will still scan the nodes outside of the "address list" boundry, but will not add them to NetXMS.

Please correct me if that is wrong

One more quesion, what format to enter the hosts in?
Comma separated, space separated?

Thanks again!

I definatelly agree that ctrl+c ctrl+v should work everywhere

For me it currently breaks from time to time even coping OIDs from MIB Explorer...