MichaelKnee

We've found spike smoothing to be a good technique, especially for things like CPU monitoring - I'm not sure you can do this in Orion but setting a monitor to only fire when the error condition exists in say 2 out of 3 job iterations works well. You still check a metric regularly but short spikes are ignored & alerts only…

1. I lead our "Automation" team we are based entirely on being multi skilled. However,the company has silo'ed teams who we rely on for specialist knowledge though we have some knowledge across nearly all I.T. disciplines including Virtualisation. Though our interest is nearly always around vendor API software development &…

Thanks for the replies chaps - great response as usual, much appreciated! Mike

Ha! yes - that's exactly what I am seeing, though I could have sworn I'd tested on SNMP V2 nodes & got the same error - I guess I must have lucked out & chosen another V3 node. Sorry I didn't mention SNMP V3 at the start - the whole point of the work I am doing at the moment is to detect if a node is SNMP V2 or V3 &…

Can you use Common Table Expressions?? I think this will work if you can - WITH CTE_AlertCount as (SELECT COUNT(*) as numAlerts FROM Nodes INNER JOIN Events ON Nodes.NodeID = Events.NetObjectID WHERE ( Events.EventType = '1' AND Events.EventTime BETWEEN DATEADD(minute, -10000, GETUTCDATE()) AND GETUTCDATE() ) GROUP BY…

Hi Bohumil - thanks for your reply, my $swis code is as follows though I'm pretty sure it's OK as the "SELECT NodeID" ... bit works OK & I get the nodeID back. We have two Solar Winds rigs by the way & the code works fine on the other one, I have tried a reboot of the problem rig but I still get the JobEngine error on any…

Thanks Tom - that's really useful information, I'm sure I can make Powershell go query for the appropriate SNMP OIDs somehow. :-)

OK - thanks for clarifying for me, much appreciated!

OK - fair enough, it's still a huge step forward & I'm very pleased it's in the SDK now!