The Datadog Agent 7.27.0 introduces a new SNMP check version in Go that has both memory and performance improvements to the Agent when monitoring devices using SNMP. The purpose of this guide is to assist in migration over to the new core check.
Agent v7.27.0 changes
Autodiscovery is now a core Agent process, and needs to be loaded in the main SNMP integration check with loader:core under the init_config, and configured in the main Datadog Agent datadog.yaml.
Direct reference to MIBs by their human readable names only are no longer supported. Instead, all OID references should be made by their numerical address, and human readable name. All Datadog shipped profiles have been updated, but custom profiles will need to be updated. Examples for migration are provided below.
The Core check does not support manually compiling MIBs to be used as a profile, therefore the following parameters are no longer supported:
mibs_folder
optimize_mib_memory_usage
enforce_mib_constraints
bulk_threshold - Removed this in favor of other GET functions
Instructions
Upgrade to Datadog Agent version 7.27+ for your corresponding Agent platform.
Update the init_config in the SNMP check to reference the new core check in snmp.d/conf.yaml.
init_config:loader:core
The following step is only applicable if you use Autodiscovery/subnet scanning: Move the configuration for each instance (subnet) from the SNMP check configuration to the main Datadog Agent datadog.yaml.
network_devices:autodiscovery:workers:100# number of workers used to discover devices concurrentlydiscovery_interval:3600# interval between each autodiscovery in secondsloader:core # use core check implementation of SNMP integration. recommendeduse_device_id_as_hostname:true# recommendedconfigs:- network_address:10.10.0.0/24 # CIDR subnetsnmp_version:2port:161community_string:'***'# enclose with single quotetags:- "key1:val1"- "key2:val2"- network_address:10.20.0.0/24snmp_version:2port:161community_string:'***'tags:- "key1:val1"- "key2:val2"
network_devices:autodiscovery:workers:100# number of workers used to discover devices concurrentlydiscovery_interval:3600# interval between each autodiscovery in secondsloader:core # use core check implementation of SNMP integration. recommendeduse_device_id_as_hostname:true# recommendedconfigs:- network_address:10.10.0.0/24 # CIDR subnetsnmp_version:3user:'user'authProtocol: 'SHA256' # choices:MD5, SHA, SHA224, SHA256, SHA384, SHA512authKey:'fakeKey'# enclose with single quoteprivProtocol: 'AES256' # choices:DES, AES (128 bits), AES192, AES192C, AES256, AES256CprivKey:'fakePrivKey'# enclose with single quotetags:- 'key1:val1'- 'key2:val2'- network_address:10.20.0.0/24snmp_version:3user:'user'authProtocol:'SHA256'authKey:'fakeKey'privProtocol:'AES256'privKey:'fakePrivKey'tags:- 'key1:val1'- 'key2:val2'
Note: Make sure you are on Agent 7.53+ for this syntax. For previous versions, see the previous config_template.yaml
Migrating custom profiles (independent of deployment)
SNMP no longer supports only listing OIDs by their human-readable name. You can reference by address (table name and index) or MIB entry address. If you have written any profiles yourself or modified any existing profiles, migrate them to the new format. Below are examples of migration.