I wager that an informal poll of IT admins across all disciplines would show that most do not bother with SNMP (Simple Network Management Protocol), and those who use SNMP do so in conjunction with basic read-only monitoring frameworks. I'd also wager that of those using SNMP, most are using SNMPv1 and have never looked into why they would want SNMPv3. This is largely because SNMP is archaic and should be put out to pasture.
I don't think any one really likes using SNMP, especially those who have to wade through vendor MIBs looking for a way to poll hardware or software for some piece of data. The fact that every vendor still supports SNMPv1, and many still use a default read-only SNMP community of "public," enabled by default, shows how apathetic we are regarding SNMP as a whole.
[ Also on InfoWorld: SDN 101: Software-defined networking in 10 easy steps | Get expert networking how-to advice from InfoWorld's Networking Deep Dive PDF special report. ]
I say this as someone who has written lots of code that directly interfaces with and manipulates hardware and software through SNMP calls. I have written plug-ins for Cacti and Nagios that use SNMP extensively to glean data out of everything from storage arrays to managed rack PDUs. I used SNMP calls in a custom Web app that finds the switch and switch port that the requesting system is connected to and allows the user to change the VLAN assignment for that port. (This turned out to be a very handy app, especially when turning up new office space with hundreds of users.)
I know SNMP very well, and I think it's long past time that we move toward a saner and more useful solution to solve the problems SNMP was developed to address. That said, I'm not sure I see anything really promising in that arena.