Currently the SNMP detector only uses configuration from the default SNMP config and definitions. It should be possible to use SNMP profiles to find a matching config.
Key points from a chat this morning:
SNMP detector should optionally use SNMP profiles in the same way that Provisiond's SNMP scan already does
The default should be not to use SNMP profiles
SNMP detector's parameterized configuration, if any, should override the corresponding elements of an SNMP profile
For example, if an SNMP profile specifies a timeout of 1800ms with 3 retries, but the detector is configured with parameters timeout=500 and retries=0, it should use a 500ms timeout with zero retries
Not sure what to do in cases where this overriding creates a nonsensical set of parameters, such as a profile specifying SNMPv3 with security level authPriv being overridden by a detector configuration specifying SNMPv1 but no community string. Maybe it's fine to declare that, for now, only timeout and retries can be overridden in this way.
If the SNMP detector is configured to use SNMP profiles, persisting the eventual fitted profile should be optional
Persisting of the fitted profile can slide in the event it turns out to be too hard
Currently the SNMP detector only uses configuration from the default SNMP config and definitions. It should be possible to use SNMP profiles to find a matching config.
Key points from a chat this morning:
SNMP detector should optionally use SNMP profiles in the same way that Provisiond's SNMP scan already does
The default should be not to use SNMP profiles
SNMP detector's parameterized configuration, if any, should override the corresponding elements of an SNMP profile
For example, if an SNMP profile specifies a timeout of 1800ms with 3 retries, but the detector is configured with parameters timeout=500 and retries=0, it should use a 500ms timeout with zero retries
Not sure what to do in cases where this overriding creates a nonsensical set of parameters, such as a profile specifying SNMPv3 with security level authPriv being overridden by a detector configuration specifying SNMPv1 but no community string. Maybe it's fine to declare that, for now, only timeout and retries can be overridden in this way.
If the SNMP detector is configured to use SNMP profiles, persisting the eventual fitted profile should be optional
Persisting of the fitted profile can slide in the event it turns out to be too hard