NetXMS Support Forum

I havent  done too much with ERL other than use it to monitor the device itself but on the ERPro  I have a few hundred devices I use it to do snmp checks on and I havent really noticed any issues with performance at all



P.S
I dont have any x devices but if it is still based on debian like the ERL then it should work... Try at your own risk

Sure,

I normally build an agent for each new release since I normally upgrade anyway ...I will work on 2.0.6 tomorrow

Can we start a thread or a place for people to post scripts.  I think it would be useful..Im sure there are alot of people that have scripts that could be useful for new comers or some that maybe trying to do the same thing.





Thanks

Its working now ... Thanks for all the help

Do i need to build the server as well or just the client  ?  How stable is the current dev branch ?

And here is node1 where i would like to calculate the status based on nodeA DCI

Here is NodeA (actual node name is RB1-ERP-POLLER) configuration That has the Agent running ping.nsm

on a side note I have noticed the DCI instance ids continue to increment and out of curiosity ran a manual instance discovery poll and got this
Running DCI instance discovery
[29.08.2016 16:13:01]    Updating instances for Icmp.LastPingTime({instance}) [28794]
[29.08.2016 16:13:01]       Existing instance "10.9.61.11 26 29 0 46 10.9.61.11" not found and will be deleted
[29.08.2016 16:13:01]       Existing instance "10.9.61.13 1 0 0 46 10.9.61.13" not found and will be deleted
[29.08.2016 16:13:01]       Existing instance "10.9.61.14 31 28 1 46 10.9.61.14" not found and will be deleted
[29.08.2016 16:13:01]       Creating new DCI for instance "10.9.61.11 39 28 0 46 10.9.61.11"
[29.08.2016 16:13:01]       Creating new DCI for instance "10.9.61.13 0 0 0 46 10.9.61.13"
[29.08.2016 16:13:01]       Creating new DCI for instance "10.9.61.14 4 32 0 46 10.9.61.14"

This seems to happen every time so im assuming after every  IntancePollingInterval which I think is set to 600 the DCI's get recreated  is this normal

it works now i was not setting the source node on node1.  But It does not seem to work unless both nodeA and node1 have dci node status checked.  And this causes nodeA to show critical as well

I did try this at first but it does not seem to have any bearing on the status of the node.  I also created a transform to return 4 if the value is over 5000 and 0 if under. Maybe i am misunderstanding the way Ping subagent works.   As i mentioned before i have set up a handful of icmp targets where i need to monitor second by second for high latency and if the latency goes above the threshold create an alert.  Right now I only see the alarm created for the node that the icmp targets are created on.  Example nodeA has the subagent to ping node1 and node2  every second if I reboot node1 I only receive and alarm for nodeA  sys_threshold_reached  whereas I would like the alarm to be created for node1 as it gets confusing when all alarms created are generated for nodeA.  I would rather not have Netxms Server ping the node since I am already monitoring latency via subagent  and because of this I would like to generate the critical alert based on the latency ping since the value will go well above 3000 if the node is actually down.  I see there is a threshold instance but the documentation is vague on its usage could this be what I need.


Thanks

i dont see any documentation for zeromq.. is this going to be used for pub/sub to alarms or will it be able to do api calls to the server using req/resp  and any zeromq client.

Is is possible to cause a node to go into critical or down status based on the results from icmp stats.  I have a subagent setup to monitor latency of several hosts  but when the threshold is met the alarm is generated for the agent and not the instance being monitored ..  I would like to generate  a critical or down status if the latency shows 10k  for that particular instance   

Wow that was fast ...   Thank you   

Just  under Infrastructure Services

Would it be possible to auto create the container if it does not exist