SNMP Trap Send

[system24seven]

Related to #396 we could add scripting functions for sending traps from Ignition to other host devices for great visibility on IT systems.

[benmusson]

I'm open to this, but I don't think I want to extend the existing device types to support sending Traps.

Traps are will need to be sent to a unique target address (i.e. port 162 instead of 161), and there are additional parameters related to sending SNMPv3 traps.

I'd rather see this as a set of new SNMP device types:

• SNMPv1 Manager
• SNMPv2c Manager
• SNMPv3 Manager

This would open the door to exposing more information from Ignition over SNMP.

[system24seven]

I agree that this would not be an extension of the device implementation, but it would still depend on using the SNMP Context that the devices share for SNMP4J.
The sender function would be a separate implementation that takes different parameters.

[benmusson]

Yup makes sense.

What would you think about suffixing the current devices types with -agent, in order to future proof the naming scheme?

This is the kind of stuff I'm okay with breaking during prerelease.

[system24seven]

I think that would be a pretty prudent idea, I feel like there will be a number of different method of using the different features of SNMP and that being more descriptive on the actual function of the devices would clear up the codebase a bunch.

[benmusson]

#398