SNMP and OID in checkmk

Hi there,

I am monitoring a Synology’s NAS with CheckMK and everything is OK.
But i would like to know if there is a way to knows which OID is used by CheckMK to get the result.

How, in checkmk, can I find the OID used to get, for example, disk status or used space on volume1.

Is there a place in GUI or in CLI i can have this information ?

Thanks,

Vincent

Yes, there is. Just follow the instructions of the documentation of custom plugins (8.3. Locating the correct OIDs)

if I understand your request, you don’t want to change anything, you want to know the OIDs used in the existing checks.

2 ways to see them:

  1. call the host on the CLI with double-verbosity "cmk -vv "
  2. check the source code of the check, i.e. open the service details and then check under checkmk/checks at master · tribe29/checkmk · GitHub or checkmk/cmk/base/plugins/agent_based at master · tribe29/checkmk · GitHub (there are two folders, because Checkmk has two different Check APIs, but you will find each check only in one of the two folders ;))

That’s exactly what I want to know because I don’t understand something.

With my NAS, if I follow the official doc, the OID to check Disk usage is 1.3.6.1.4.1.6574.3.4 (even if I don’t understand).
But, it seems that this OID is not implemented in my NAS… but checkmk correctly view used space…

So I don’t understand how it could do this…

So what is the output of “cmk -vv <NAS_hostname_in_cmk>” ?
Please use the code tags when replying, the reply will be long :slight_smile:

OMD[test]:~$ cmk -vv nas-test
Checkmk version 2.1.0p3
Try license usage history update.
Trying to acquire lock on /omd/sites/test/var/check_mk/license_usage/next_run
Got lock on /omd/sites/test/var/check_mk/license_usage/next_run
Trying to acquire lock on /omd/sites/test/var/check_mk/license_usage/history.json
Got lock on /omd/sites/test/var/check_mk/license_usage/history.json
Next run time has not been reached yet. Abort.
Releasing lock on /omd/sites/test/var/check_mk/license_usage/history.json
Released lock on /omd/sites/test/var/check_mk/license_usage/history.json
Releasing lock on /omd/sites/test/var/check_mk/license_usage/next_run
Released lock on /omd/sites/test/var/check_mk/license_usage/next_run
+ FETCHING DATA
  Source: SourceType.HOST/FetcherType.SNMP
[cpu_tracking] Start [7f3c223bdeb0]
[SNMPFetcher] Fetch with cache settings: SNMPFileCache(nas-test, base_path=/omd/sites/test/tmp/check_mk/data_source_cache/snmp, max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=False, use_outdated=False, simulation=False)
Not using cache (Too old. Age is 33 sec, allowed is 0 sec)
[SNMPFetcher] Execute data source
  SNMP scan:
       Getting OID .1.3.6.1.2.1.1.1.0: Running 'snmpget -v1 -c public -m "" -M "" -On -OQ -Oe -Ot 172.29.4.30 .1.3.6.1.2.1.1.1.0'
SNMP answer: ==> ["Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64"]
b'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Getting OID .1.3.6.1.2.1.1.2.0: Running 'snmpget -v1 -c public -m "" -M "" -On -OQ -Oe -Ot 172.29.4.30 .1.3.6.1.2.1.1.2.0'
SNMP answer: ==> [.1.3.6.1.4.1.8072.3.2.10]
b'.1.3.6.1.4.1.8072.3.2.10'
       Using cached OID .1.3.6.1.2.1.1.2.0: '.1.3.6.1.4.1.8072.3.2.10'
       Using cached OID .1.3.6.1.2.1.1.2.0: '.1.3.6.1.4.1.8072.3.2.10'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.2.0: '.1.3.6.1.4.1.8072.3.2.10'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Getting OID .1.3.6.1.2.1.2.2.1.*: Running 'snmpgetnext -Cf -v1 -c public -m "" -M "" -On -OQ -Oe -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1'
SNMP answer: ==> [1]
b'1'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.2.0: '.1.3.6.1.4.1.8072.3.2.10'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.2.0: '.1.3.6.1.4.1.8072.3.2.10'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
       Using cached OID .1.3.6.1.2.1.1.1.0: 'Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64'
   SNMP scan found                    hr_mem if snmp_uptime ucd_cpu_load
Trying to acquire lock on /omd/sites/test/tmp/check_mk/snmp_scan_cache/nas-test.172.29.4.30
Got lock on /omd/sites/test/tmp/check_mk/snmp_scan_cache/nas-test.172.29.4.30
Releasing lock on /omd/sites/test/tmp/check_mk/snmp_scan_cache/nas-test.172.29.4.30
Released lock on /omd/sites/test/tmp/check_mk/snmp_scan_cache/nas-test.172.29.4.30
hr_cpu: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.25.3.3.1.2'
ucd_cpu_load: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.2021.10.1.5'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.2021.10.1.6'
hr_fs: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.25.2.3.1.2'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.25.2.3.1.3'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.25.2.3.1.4'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.25.2.3.1.5'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.25.2.3.1.6'
hr_mem: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Already fetched OID: .1.3.6.1.2.1.25.2.3.1.2
Already fetched OID: .1.3.6.1.2.1.25.2.3.1.3
Already fetched OID: .1.3.6.1.2.1.25.2.3.1.4
Already fetched OID: .1.3.6.1.2.1.25.2.3.1.5
Already fetched OID: .1.3.6.1.2.1.25.2.3.1.6
if: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.1'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.2'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.3'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.5'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.8'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.10'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.11'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.12'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.13'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.14'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.16'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.17'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.18'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.19'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.20'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.21'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.2.2.1.6'
snmp_info: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.1.1'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.1.4'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.1.5'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.1.6'
snmp_uptime: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.1.3'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.2.1.25.1.1'
synology_disks: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.2.1.1.2'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.2.1.1.3'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.2.1.1.5'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.2.1.1.6'
synology_fans: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.1.4.1'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.1.4.2'
synology_info: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.1.5.1'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.1.5.2'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.1.5.3'
synology_raid: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.3.1.1.2'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.3.1.1.3'
synology_status: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.1.1'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.1.3'
synology_update: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Already fetched OID: .1.3.6.1.4.1.6574.1.5.3
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.6574.1.5.4'
ucd_diskio: Fetching data (SNMP walk cache is enabled: Use any locally cached information)
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.2021.13.15.1.1.1'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.2021.13.15.1.1.2'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.2021.13.15.1.1.3'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.2021.13.15.1.1.4'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.2021.13.15.1.1.5'
Running 'snmpwalk -v1 -c public -m "" -M "" -Cc -OQ -OU -On -Ot 172.29.4.30 .1.3.6.1.4.1.2021.13.15.1.1.6'
Write data to cache file /omd/sites/test/tmp/check_mk/data_source_cache/snmp/checking/nas-test
Trying to acquire lock on /omd/sites/test/tmp/check_mk/data_source_cache/snmp/checking/nas-test
Got lock on /omd/sites/test/tmp/check_mk/data_source_cache/snmp/checking/nas-test
Releasing lock on /omd/sites/test/tmp/check_mk/data_source_cache/snmp/checking/nas-test
Released lock on /omd/sites/test/tmp/check_mk/data_source_cache/snmp/checking/nas-test
[cpu_tracking] Stop [7f3c223bdeb0 - Snapshot(process=posix.times_result(user=0.08000000000000007, system=0.21000000000000002, children_user=0.04, children_system=0.37, elapsed=2.0100000016391277))]
  Source: SourceType.HOST/FetcherType.PIGGYBACK
[cpu_tracking] Start [7f3c223bda60]
[PiggybackFetcher] Fetch with cache settings: NoCache(nas-test, base_path=/omd/sites/test/tmp/check_mk/data_source_cache/piggyback, max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=True, use_outdated=False, simulation=False)
Not using cache (Cache usage disabled)
[PiggybackFetcher] Execute data source
No piggyback files for 'nas-test'. Skip processing.
No piggyback files for '172.29.4.30'. Skip processing.
Not using cache (Cache usage disabled)
[cpu_tracking] Stop [7f3c223bda60 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))]
+ PARSE FETCHER RESULTS
  Source: SourceType.HOST/FetcherType.SNMP
No persisted sections
  -> Add sections: ['hr_cpu', 'hr_fs', 'hr_mem', 'if', 'snmp_info', 'snmp_uptime', 'synology_disks', 'synology_fans', 'synology_info', 'synology_raid', 'synology_status', 'synology_update', 'ucd_cpu_load', 'ucd_diskio']
  Source: SourceType.HOST/FetcherType.PIGGYBACK
No persisted sections
  -> Add sections: []
Received no piggyback data
Received no piggyback data
[cpu_tracking] Start [7f3c2232dca0]
value store: synchronizing
Trying to acquire lock on /omd/sites/test/tmp/check_mk/counters/nas-test
Got lock on /omd/sites/test/tmp/check_mk/counters/nas-test
value store: loading from disk
Releasing lock on /omd/sites/test/tmp/check_mk/counters/nas-test
Released lock on /omd/sites/test/tmp/check_mk/counters/nas-test
CPU load             15 min load: 0.05, 15 min load per core: 0.05 (1 cores)
CPU utilization      Total CPU: 0.5%
Disk Drive 1         Status: OK, Temperature: 28 °C, Model: WD30EFRX-68EUZN0
Disk Drive 2         Status: OK, Temperature: 31 °C, Model: DT01ACA300
Disk Drive 3         Status: OK, Temperature: 29 °C, Model: WD40EFRX-68N32N0
Disk Drive 4         Status: OK, Temperature: 28 °C, Model: WD30EFRX-68EUZN0
Disk Drive 5         Status: OK, Temperature: 28 °C, Model: WD30EFRX-68EUZN0
Disk IO dm-0         [55], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO loop0        [46], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO loop1        [47], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO loop2        [48], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO loop3        [49], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO loop4        [50], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO loop5        [51], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO loop6        [52], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO loop7        [53], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO md0          [37], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO md1          [38], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO md2          [54], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram0         [1], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram1         [2], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram10        [11], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram11        [12], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram12        [13], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram13        [14], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram14        [15], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram15        [16], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram2         [3], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram3         [4], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram4         [5], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram5         [6], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram6         [7], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram7         [8], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram8         [9], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO ram9         [10], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sda          [29], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sda1         [30], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sda2         [31], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sda5         [32], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdb          [33], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdb1         [34], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdb2         [35], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdb5         [36], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdc          [17], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdc1         [18], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdc2         [19], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdc5         [20], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdd          [21], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdd1         [22], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdd2         [23], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sdd5         [24], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sde          [25], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sde1         [26], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sde2         [27], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO sde5         [28], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO synoboot     [43], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO synoboot1    [44], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO synoboot2    [45], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO zram0        [39], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO zram1        [40], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO zram2        [41], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Disk IO zram3        [42], Read: 0.00 B/s, Write: 0.00 B/s, Read operations: 0.00 1/s, Write operations: 0.00 1/s
Fan CPU              No failure reported
Fan System           No failure reported
Filesystem /         46.33% used (1.05 of 2.28 GB), trend: 0.00 B / 24 hours
Filesystem /dev/shm  0.0004% used (4.00 kB of 993.41 MB), trend: 0.00 B / 24 hours
Filesystem /run      0.55% used (5.44 of 993.41 MB), trend: +10.91 kB / 24 hours
Filesystem /run/cgmanager/fs 0% used (0.00 B of 100.00 kB), trend: 0.00 B / 24 hours
Filesystem /sys/fs/cgroup 0% used (0.00 B of 4.00 kB), trend: 0.00 B / 24 hours
Filesystem /tmp      0.11% used (1.13 of 993.41 MB), trend: 0.00 B / 24 hours
Filesystem /volume1  0.002% used (52.17 MB of 2.62 TB), trend: 0.00 B / 24 hours
Info                 Model: DS1515+, S/N: 1591MQN705901, OS Version: DSM 6.2-25556
Interface 6          [eth3], (up), MAC: 00:11:32:4E:07:E4, Speed: 100 MBit/s, In: 3.25 kB/s (0.03%), Out: 1.63 kB/s (0.01%)
Memory               Total (RAM + Swap): 14.92% - 297 MiB of 1.94 GiB RAM, RAM: 14.92% - 297 MiB of 1.94 GiB, Swap: 0% - 0 B of 3.16 GiB
RAID Volume 1        Status: OK
SNMP Info            Linux nas-230 3.10.105 #25556 SMP Sat Aug 28 02:15:59 CST 2021 x86_64, nas-230, Unknown, admin@diskstation
Status               System state OK, Power State OK
Update               Update Status: Unavailable, Current Version: DSM 6.2-25556
Uptime               Up since Jun 03 2022 14:31:31, Uptime: 25 days 1 hour
value store: synchronizing
Trying to acquire lock on /omd/sites/test/tmp/check_mk/counters/nas-test
Got lock on /omd/sites/test/tmp/check_mk/counters/nas-test
value store: already loaded
value store: writing to disk
Releasing lock on /omd/sites/test/tmp/check_mk/counters/nas-test
Released lock on /omd/sites/test/tmp/check_mk/counters/nas-test
No piggyback files for 'nas-test'. Skip processing.
No piggyback files for '172.29.4.30'. Skip processing.
[cpu_tracking] Stop [7f3c2232dca0 - Snapshot(process=posix.times_result(user=0.06000000000000005, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.06999999657273293))]
[snmp] Success, execution time 2.1 sec | execution_time=2.080 user_time=0.140 system_time=0.210 children_user_time=0.040 children_system_time=0.370 cmk_time_snmp=1.310 cmk_time_agent=0.000

this part is for the disk usage (I’m assuming you mean “Filesystem ” services) - where do you get the OID 1.3.6.1.4.1.6574.3.4 from?

Hi @gstolz ,

I search yesterday after your last post and I thought I understood that these were indeed the OIDs that were used by check_mk

And the OID 1.3.6.1.4.1.6574.3.4 come from the official Synology documentation (page 8) :

Vincent

ok - I don’t know about how close Synology follows its own documentation, but obviously they support the hr_fs generic OIDs and “cmk -vv” showed you the OIDs. Does this solve your original question or is there still something you need to know?

I don’t know either… Afterwards, I tell myself that my NAS may be too old and hasn’t had a firmware update to have these OIDs…
But as you say, they seems to support hr_fs generic OIDs…

and that answers my question :wink:

Thanks for your time @gstolz