Hello,
Was wondering if any of you have had issues with snmp bandwidth polling on netxms. Huge spikes showing up at a random basis is quite annoying - whether it being because of counter resets or what not. (screenshots attached)
My question is, is there a way to bypass this? I mean i have seen similar posts and found one of the devs mentioning a transformation script, which essentially just limits the maximum value your network can handle, then returns the max bandwidth your interface can handle ie
if ($1 > 1000)
return 1000;
return $1;
OR some sort of a fixed value you assign via script, which I'd rather not use
Anyone got any ideas? is it possible to return the last polled value if the current poll exceeded the limit? or are there any other methods /ideas? thanks in advance
Was wondering if any of you have had issues with snmp bandwidth polling on netxms. Huge spikes showing up at a random basis is quite annoying - whether it being because of counter resets or what not. (screenshots attached)
My question is, is there a way to bypass this? I mean i have seen similar posts and found one of the devs mentioning a transformation script, which essentially just limits the maximum value your network can handle, then returns the max bandwidth your interface can handle ie
if ($1 > 1000)
return 1000;
return $1;
OR some sort of a fixed value you assign via script, which I'd rather not use
Anyone got any ideas? is it possible to return the last polled value if the current poll exceeded the limit? or are there any other methods /ideas? thanks in advance