The SNMPRawCollector is designed for collecting data from SNMP-enables devices, using a set of specified OIDs
Below is an example configuration for the SNMPRawCollector. The collector can collect data any number of devices by adding configuration sections under the devices header. By default the collector will collect every 60 seconds. This might be a bit excessive and put unnecessary load on the devices being polled. You may wish to change this to every 300 seconds. However you need modify your graphite data retentions to handle this properly.
# Options for SNMPRawCollector enabled = True interval = 60 [devices] # Start the device configuration # Note: this name will be used in the metric path. [[my-identification-for-this-host]] host = localhost port = 161 community = public # Start the OID list for this device # Note: the value part will be used in the metric path. [[[oids]]] 18.104.22.168.4.1.2021.10.1.3.1 = cpu.load.1min 22.214.171.124.4.1.2021.10.1.3.2 = cpu.load.5min 126.96.36.199.4.1.2021.10.1.3.3 = cpu.load.15min # If you want another host, you can. But you probably won't need it. [[another-identification]] host = router1.example.com port = 161 community = public [[[oids]]] oid = metric.path oid = metric.path
Note: If you modify the SNMPRawCollector configuration, you will need to restart diamond.
- pysmnp (which depends on pyasn1 0.1.7 and pycrypto)
|byte_unit||byte||Default numeric output(s)||str|
|enabled||False||Enable collecting these metrics||bool|
|measure_collector_time||False||Collect the collector run time in ms||bool|
|metrics_blacklist||None||Regex to match metrics to block. Mutually exclusive with metrics_whitelist||NoneType|
|metrics_whitelist||None||Regex to match metrics to transmit. Mutually exclusive with metrics_blacklist||NoneType|
|retries||3||Number of times to retry before bailing||int|
|timeout||5||Seconds before timing out the snmp connection||int|