[Jrds-developpers] dsType discovered by dosnmpprobe

[olc <ol...@gl...>]

Hi -

I'm trying to generate some SNMP probes.

Using the provided example from http://jrds.fr/snmp_probes, dsType are 
shown as expected:

$ java -jar ./WEB-INF/lib/boot.jar dosnmpprobe --Name DiskIo64 
--probeName 'io64-${index}' --index UCD-DISKIO-MIB::diskIODevice 
--graphs DiskIoGraphBytes,DiskIoGraphReq,DiskIoGraphSize --collect 
UCD-DISKIO-MIB::diskIONReadX,UCD-DISKIO-MIB::diskIONWrittenX,UCD-DISKIO-MIB::diskIOReads,UCD-DISKIO-MIB::diskIOWrites
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE probedesc PUBLIC "-//jrds//DTD Probe Description//EN" 
"urn:jrds:probedesc">
<probedesc>
     <name>DiskIo64</name>
     <probeName>io64-${index}</probeName>
     <probeClass>jrds.probe.snmp.RdsIndexedSnmpRrd</probeClass>
     <specific name="indexOid">1.3.6.1.4.1.2021.13.15.1.1.2</specific>
     <ds>
         <dsName>diskIONReadX</dsName>
         <dsType>COUNTER</dsType>
         <oid>1.3.6.1.4.1.2021.13.15.1.1.12</oid>
     </ds>
     <ds>
         <dsName>diskIONWrittenX</dsName>
         <dsType>COUNTER</dsType>
         <oid>1.3.6.1.4.1.2021.13.15.1.1.13</oid>
     </ds>
     <ds>
         <dsName>diskIOReads</dsName>
         <dsType>COUNTER</dsType>
         <oid>1.3.6.1.4.1.2021.13.15.1.1.5</oid>
     </ds>
     <ds>
         <dsName>diskIOWrites</dsName>
         <dsType>COUNTER</dsType>
         <oid>1.3.6.1.4.1.2021.13.15.1.1.6</oid>
     </ds>
     <graphs>
         <name>DiskIoGraphBytes</name>
         <name>DiskIoGraphReq</name>
         <name>DiskIoGraphSize</name>
     </graphs>
</probedesc>


But when I try to generate a problem for a custom probe, I can't figure 
out why it is missing:

$ java -jar ./WEB-INF/lib/boot.jar dosnmpprobe --Name Ntp  --probeName 
'ntp' --graphs NtpDelay,NtpOffset,NtpJitter --collect 
CUSTOM-NTP-MIB::delay,CUSTOM-NTP-MIB::offset,CUSTOM-NTP-MIB::jitter

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE probedesc PUBLIC "-//jrds//DTD Probe Description//EN" 
"urn:jrds:probedesc">
<probedesc>
     <name>Ntp</name>
     <probeName>ntp</probeName>
     <probeClass>jrds.probe.snmp.RdsSnmpSimple</probeClass>
     <specific name="requester">simple</specific>
     <ds>
         <dsName>delay</dsName>
         <oid>1.3.6.1.3.54.1.0</oid>
     </ds>
     <ds>
         <dsName>offset</dsName>
         <oid>1.3.6.1.3.54.1.1</oid>
     </ds>
     <ds>
         <dsName>jitter</dsName>
         <oid>1.3.6.1.3.54.1.2</oid>
     </ds>
     <graphs>
         <name>NtpDelay</name>
         <name>NtpOffset</name>
         <name>NtpJitter</name>
     </graphs>
</probedesc>

Here is an snmpwalk for my custom MIB:

$ snmpwalk -v 2c -c public wopr-1 CUSTOM-NTP-MIB::ntp
CUSTOM-NTP-MIB::delay = INTEGER: 260
CUSTOM-NTP-MIB::offset = INTEGER: 2974
CUSTOM-NTP-MIB::jitter = INTEGER: 10029

I suspect that INTEGER might not be the appropriate type (I'm a noobs 
with MIBS) but I have also tested to generate a probe for 
HOST-RESOURCES-MIB::hrSystemNumUsers which is a Gauge32 type and the 
dsType is also missing.

Not a big deal of course as it is easy to add those missing dsType by 
hand. I just wanna know if I'm doing something wrong. Any 
idea/suggestion will be greatly welcome! Thanks in anticipation.

Regards,
-- 
Olivier