Severity
3 - Can work around the issue but this function should be inherent to OpsMgr.
Applicability
5 - I can see where this suggestion would help most admins / environments.
The SNMP Receiver of OpsMgr as it is currently lacks maybe the most important feature: Receive ANY SNMP Trap. Currently you just can't send SNMP Traps to OpsMgr manually, it only accepts them by Network Devices. And even then, we tried to discover a machine as a network device, works. When we forge SNMP Traps on it, and send them to OpsMgr they will be ignored.
Second thing, if you create a Rule/Mon in the OpsMgr Console, you can't set Network Devices as a target. At least here. And if you don't use the Network Devices class, and use the Network Devices Group you get an Error that the IPAddress$ property is not available and was expected. And why should I only receive SNMP Traps from Network Devices anyway?
I guess the way it works now is due to security considerations.
However, due to the kickass SDK we were able to work around that problem. But having to go from creating a simple Alert-Rule to Developing is kind of an overkill for a simple feature like: Receive SNMP Traps from all devices, generate alerts.