Do I need SAM? Couldn't I just recreate everything SAM does using UnDP's?

After my initial play around with SAM 6.2.3 it struck me that maybe I could do without the expense of this module because perhaps I could get all the same polling data if I went to find out the correct OID for each component monitor SAM provides.

Would I be correct in saying that if you were prepared to put in the work you could get all the data gathered by SAM by just working out which OID's to poll and adding a load of resources to a node details page?

What does SAM offer me that's not already possible in NPM?

Find more posts tagged with

custom oid poller

npm

universal_device_pollers

Accepted answers

All comments

jeff.stewart

The SAM SNMP component monitor only supports Get & Get-Next, so it is limited in functionality when compared to the Universal Device Poller in NPM.

noobes

OK so NPM 1 - SAM 0. Is it just the fact that SAM has these certain OIDs bundled up in templates that is its main draw?jeff.stewart

jeff.stewart

aLTeReGo would have been the PM to add the SNMP component monitor to SAM so he will have the best answer. My best guess is that it was mainly added to support specific application monitoring for applications that only expose statistical data via SNMP (most don't, but there are a few as you can see based on the application templates out there). It wasn't built as an intent to replace or cover all of the functionality within the UnDP.

Jeff

aLTeReGo

Much of the data SAM collects is retrieved via other protocols other than SNMP. SNMP is extremely limited, as most applications don't expose any information via SNMP.

tinmann0715

Umm, no, I guess not? You could program a lot of it yourself and miss out on so, so, so, so, much! In the end you'll be chasing your tail as you are constantly programming and updating as you are busily fill gaps from now until the end of time. So good luck with that.