I know the mib is working because when I do an snmpwalk i get the following 
output.

~/snmp_exporter/generator$ snmpwalk -v2c -c public *.*.*.* 
1.3.6.1.4.1.6574.3
SNMPv2-SMI::enterprises.6574.3.1.1.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.6574.3.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.6574.3.1.1.2.0 = STRING: "Volume 1"
SNMPv2-SMI::enterprises.6574.3.1.1.2.1 = STRING: "Storage Pool 1"
SNMPv2-SMI::enterprises.6574.3.1.1.3.0 = INTEGER: 1
SNMPv2-SMI::enterprises.6574.3.1.1.3.1 = INTEGER: 1
SNMPv2-SMI::enterprises.6574.3.1.1.4.0 = Counter64: 14395893346304
SNMPv2-SMI::enterprises.6574.3.1.1.4.1 = Counter64: 398458880
SNMPv2-SMI::enterprises.6574.3.1.1.5.0 = Counter64: 15355710676992
SNMPv2-SMI::enterprises.6574.3.1.1.5.1 = Counter64: 15995942993920
SNMPv2-SMI::enterprises.6574.3.1.1.6.0 = INTEGER: 0
SNMPv2-SMI::enterprises.6574.3.1.1.6.1 = INTEGER: 0

On Monday, September 30, 2024 at 9:06:17 AM UTC-4 Mitchell Laframboise 
wrote:

> Thank you for the explanations... I've checked the mibs and that metric is 
> included as an object along with others like raidFreeSize that are also not 
> being included in the generated snmp.yml  I'm using the latest verison of 
> snmp-exporter 0.26.0 Im wondering if the generator is broken?
>
> On Monday, September 30, 2024 at 8:48:11 AM UTC-4 Brian Candler wrote:
>
>> > Since the generator.yml has that metric in overrides, shouldn't it be 
>> generated?
>>
>> No. Overrides only change how a metric is rendered; if there's no 
>> matching metric in the MIB then there's nothing to override.
>>
>> On Monday 30 September 2024 at 13:45:57 UTC+1 Brian Candler wrote:
>>
>>> > I looked at the sample snmp.yml from Github that I assume is generated 
>>> from the default generator.yml and I see that the "raidTotalSize" metric is 
>>> included, but when I check my snmp.yml that metric isn't included.
>>>
>>> Either something is different in your generator.yml, or something is 
>>> different in the set of MIBs you are making available to generator. If you 
>>> can solve that, it would avoid you having to hack snmp.yml manually, and 
>>> might be covering up some other problem.
>>>
>>> > the dashboard is still not picking it up.  I guess I'm going to have 
>>> to ask the Grafana community.
>>>
>>> It will be a problem with the queries configured in Grafana, and if they 
>>> make use of Grafana variables they may not be set the way you expect. So 
>>> indeed, Grafana is where you need to look. Using (three dots) > Inspect > 
>>> Query on a panel, you should be able to see what query it is sending.
>>>
>>> On Monday 30 September 2024 at 13:39:30 UTC+1 Mitchell Laframboise wrote:
>>>
>>>> I looked at the sample snmp.yml from Github that I assume is generated 
>>>> from the default generator.yml and I see that the "raidTotalSize" metric 
>>>> is 
>>>> included, but when I check my snmp.yml that metric isn't included.  So I 
>>>> edited the snmp.yml to include that metric and now Prometheus is scraping 
>>>> that data, but the dashboard is still not picking it up.  I guess I'm 
>>>> going 
>>>> to have to ask the Grafana community.
>>>>
>>>> On Monday, September 30, 2024 at 3:03:00 AM UTC-4 Brian Candler wrote:
>>>>
>>>>> I can't see what you're looking at, because:
>>>>>
>>>>> 1. You've shown your generator.yml, but you've not shown the snmp.yml 
>>>>> output that generator creates.
>>>>> 2. You've not said how the output snmp.yml is different from the 
>>>>> supplied snmp.yml
>>>>> 3. You've not said what version of snmp_exporter you're using, so I 
>>>>> can't look at the supplied snmp.yml.
>>>>>
>>>>> Have you tried using *exactly* the same synology section in your 
>>>>> generator.yml as in the supplied generator.yml, and then comparing the 
>>>>> snmp.yml output?
>>>>>
>>>>> Are you getting any errors or warnings from generator when you run it? 
>>>>> If so, maybe you've not got the correct versions of MIBs available. The 
>>>>> Makefile in the generator directory shows where it downloads them from 
>>>>> when 
>>>>> building the default MIBs.
>>>>>
>>>>> On Monday 30 September 2024 at 03:20:32 UTC+1 Mitchell Laframboise 
>>>>> wrote:
>>>>>
>>>>>>   Hi.  I'm having issues with another metric.  raidTotalSize 
>>>>>>
>>>>>> its in the default generator.yml under the synology module in 
>>>>>> overrides but when I generate the snmp.yml it doesn't put the metric in 
>>>>>> there???   I can't figure out why
>>>>>>
>>>>>> Here is my generator.yml file
>>>>>>
>>>>>> ---
>>>>>> auths:
>>>>>>   public_v1:
>>>>>>     version: 1
>>>>>>   public_v2:
>>>>>>     version: 2
>>>>>>
>>>>>> modules:
>>>>>>   # Default IF-MIB interfaces table with ifIndex.
>>>>>>   if_mib:
>>>>>>     walk: [sysUpTime, interfaces, ifXTable]
>>>>>>
>>>>>>     lookups:
>>>>>>       - source_indexes: [ifIndex]
>>>>>>         lookup: ifAlias
>>>>>>       - source_indexes: [ifIndex]
>>>>>>         # Uis OID to avoid conflict with PaloAlto PAN-COMMON-MIB.
>>>>>>         lookup: 1.3.6.1.2.1.2.2.1.2 # ifDescr
>>>>>>       - source_indexes: [ifIndex]
>>>>>>         # Use OID to avoid conflict with Netscaler NS-ROOT-MIB.
>>>>>>         lookup: 1.3.6.1.2.1.31.1.1.1.1 # ifName
>>>>>>     overrides:
>>>>>>       ifAlias:
>>>>>>         ignore: true # Lookup metric
>>>>>>       ifDescr:
>>>>>>         ignore: true # Lookup metric
>>>>>>       ifName:
>>>>>>         ignore: true # Lookup metric
>>>>>>       ifType:
>>>>>>         type: EnumAsInfo
>>>>>> # Synology
>>>>>> #
>>>>>> # Synology MIBs can be found here:
>>>>>> #   http://www.synology.com/support/snmp_mib.php
>>>>>> #   
>>>>>> http://dedl.synology.com/download/Document/MIBGuide/Synology_MIB_File.zip
>>>>>> #
>>>>>> # Tested on RS2414rp+ NAS
>>>>>> #
>>>>>>   synology:
>>>>>>     walk:
>>>>>>       - 1.3.6.1.4.1.6574.1       # synoSystem
>>>>>>       - 1.3.6.1.4.1.6574.2       # synoDisk
>>>>>>       - 1.3.6.1.4.1.6574.3       # synoRaid
>>>>>>       - 1.3.6.1.4.1.6574.4       # synoUPS
>>>>>>       - 1.3.6.1.4.1.6574.5       # synologyDiskSMART
>>>>>>       - 1.3.6.1.4.1.6574.6       # synologyService
>>>>>>       - 1.3.6.1.4.1.6574.101     # storageIO
>>>>>>       - 1.3.6.1.4.1.6574.102     # spaceIO
>>>>>>       - 1.3.6.1.4.1.6574.104     # synologyiSCSILUN
>>>>>>     lookups:
>>>>>>       - source_indexes: [spaceIOIndex]
>>>>>>         lookup: spaceIODevice
>>>>>>         drop_source_indexes: true
>>>>>>       - source_indexes: [storageIOIndex]
>>>>>>         lookup: storageIODevice
>>>>>>         drop_source_indexes: true
>>>>>>       - source_indexes: [serviceInfoIndex]
>>>>>>         lookup: serviceName
>>>>>>         drop_source_indexes: true
>>>>>>       - source_indexes: [diskIndex]
>>>>>>         lookup: diskID
>>>>>>         drop_source_indexes: true
>>>>>>       - source_indexes: [raidIndex]
>>>>>>         lookup: raidName
>>>>>>         drop_source_indexes: true
>>>>>>     overrides:
>>>>>>       diskModel:
>>>>>>         type: DisplayString
>>>>>>       diskSMARTAttrName:
>>>>>>         type: DisplayString
>>>>>>       diskSMARTAttrStatus:
>>>>>>         type: DisplayString
>>>>>>       diskSMARTInfoDevName:
>>>>>>         type: DisplayString
>>>>>>       diskType:
>>>>>>         type: DisplayString
>>>>>>       modelName:
>>>>>>         type: DisplayString
>>>>>>       raidFreeSize:
>>>>>>         type: gauge
>>>>>>       raidName:
>>>>>>         type: DisplayString
>>>>>>       raidTotalSize:
>>>>>>         type: gauge
>>>>>>       serialNumber:
>>>>>>         type: DisplayString
>>>>>>       serviceName:
>>>>>>         type: DisplayString
>>>>>>       version:
>>>>>>         type: DisplayString
>>>>>>
>>>>>> # UCD-SNMP-MIB
>>>>>> #
>>>>>> # University of California, Davis extensions. Commonly used for host
>>>>>> # metrics. For example, Linux-based systems, DD-WRT, Synology,
>>>>>> # Mikrotik, Kemp LoadMaster, etc.
>>>>>> #
>>>>>> # http://www.net-snmp.org/docs/mibs/UCD-SNMP-MIB.txt
>>>>>> #
>>>>>>   ucd_la_table:
>>>>>>     walk:
>>>>>>       - 1.3.6.1.4.1.2021.10.1.2 # laNames
>>>>>>       - 1.3.6.1.4.1.2021.10.1.5 # laLoadInt
>>>>>>       - 1.3.6.1.4.1.2021.10.1.6 # laLoadFloat
>>>>>>     lookups:
>>>>>>       - source_indexes: [laIndex]
>>>>>>         lookup: laNames
>>>>>>         drop_source_indexes: true
>>>>>>   ucd_memory:
>>>>>>     walk:
>>>>>>       - 1.3.6.1.4.1.2021.4 # memory
>>>>>>   ucd_system_stats:
>>>>>>     walk:
>>>>>>       - 1.3.6.1.4.1.2021.11 # systemStats
>>>>>>
>>>>>> any help would be appreciated.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>> On Sunday, September 29, 2024 at 4:44:02 PM UTC-4 Mitchell 
>>>>>> Laframboise wrote:
>>>>>>
>>>>>>> Thanks for your reply.  I was using the default generator.yml which 
>>>>>>> lists an override of ifName and ignore was set to "true"  I removed 
>>>>>>> those 
>>>>>>> lines before generating the snmp.yml and was able to query ifName.  
>>>>>>>
>>>>>>> Thank you!
>>>>>>>
>>>>>>> On Sunday, September 29, 2024 at 4:17:09 PM UTC-4 Brian Candler 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> >  I am successful in querying the metrics in Prometheus
>>>>>>>>
>>>>>>>> Which ones in particular *are* you able to see?
>>>>>>>>
>>>>>>>> > I did some more queries and found that I'm unable to return 
>>>>>>>> ifName?
>>>>>>>>
>>>>>>>> Please explain exactly what you're doing when you say "unable to 
>>>>>>>> return". If you're going to the Prometheus web interface (usually at 
>>>>>>>> x.x.x.x:9090) and entering "ifName" as the query and hitting Enter, 
>>>>>>>> and 
>>>>>>>> getting no results, then it seems like you're not successfully 
>>>>>>>> scraping the 
>>>>>>>> if_mib from any targets. However if you're getting some other metrics 
>>>>>>>> like 
>>>>>>>> ifHCInOctets from the if_mib, then maybe the way you built snmp.yml 
>>>>>>>> from 
>>>>>>>> generator.yml is broken.
>>>>>>>>
>>>>>>>> You'll need to work out what's happening. In the same Prometheus 
>>>>>>>> web interface go to Status > Targets as a starting point. If it says 
>>>>>>>> the 
>>>>>>>> target is "up" then try doing exactly the same scrape manually:
>>>>>>>> curl -v 'x.x.x.x:9116/snmp?target=y.y.y.y&module=zzzz&auth=aaaa'
>>>>>>>>
>>>>>>>> and/or point a web browser at x.x.x.x:9116/snmp/status as I 
>>>>>>>> suggested before. Also look at snmp_exporter's stdout ("systemctl 
>>>>>>>> status 
>>>>>>>> snmp_exporter" if you're running it under systemd).
>>>>>>>>
>>>>>>>> Basically, you need to divide and conquer. If ifName not being 
>>>>>>>> returned from any targets, then is it a problem with your snmp.yml, or 
>>>>>>>> with 
>>>>>>>> your prometheus scrape config, or something else? You haven't shown 
>>>>>>>> your 
>>>>>>>> scrape config, so the problem could be there. You also haven't shown 
>>>>>>>> the 
>>>>>>>> snmp.yml which came from your generator.yml.
>>>>>>>>
>>>>>>>> On Sunday 29 September 2024 at 14:40:33 UTC+1 Mitchell Laframboise 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi there,
>>>>>>>>>
>>>>>>>>>   I did some more queries and found that I'm unable to return 
>>>>>>>>> ifName?  Im walking that specific OID so I don't understand?
>>>>>>>>>
>>>>>>>>> Can you help
>>>>>>>>>
>>>>>>>>> On Sunday, September 29, 2024 at 9:23:37 AM UTC-4 Mitchell 
>>>>>>>>> Laframboise wrote:
>>>>>>>>>
>>>>>>>>>> Thanks Brian.  I am successful in querying the metrics in 
>>>>>>>>>> Prometheus, so I will check out the Grafana community for support.
>>>>>>>>>>
>>>>>>>>>> On Sunday, September 29, 2024 at 9:03:12 AM UTC-4 Brian Candler 
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> First, do a query in the Prometheus web interface (for example, 
>>>>>>>>>>> just "ifPhysAddress"). If you see no answers, then you need to 
>>>>>>>>>>> drill down 
>>>>>>>>>>> into your metrics collection. Check the query "up" to see if SNMP 
>>>>>>>>>>> scraping 
>>>>>>>>>>> is successful. If it's not, then check logs from snmp_exporter 
>>>>>>>>>>> ("journalctl 
>>>>>>>>>>> -eu snmp_exporter), or use the test web interface at 
>>>>>>>>>>> <your-snmp-exporter>:9116/snmp/status
>>>>>>>>>>>
>>>>>>>>>>> If the metrics collection into Prometheus is working, meaning 
>>>>>>>>>>> that you have a problem with Grafana, then please seek Grafana 
>>>>>>>>>>> support from 
>>>>>>>>>>> the Grafana Community <https://community.grafana.com/>.
>>>>>>>>>>>
>>>>>>>>>>> On Sunday 29 September 2024 at 13:57:12 UTC+1 Mitchell 
>>>>>>>>>>> Laframboise wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Good morning group,  I have only some of this public dashboard 
>>>>>>>>>>>> working and I'm wondering how to get the rest up and running.  I 
>>>>>>>>>>>> am 
>>>>>>>>>>>> starting with the interface.  Its showing no data, so I was hoping 
>>>>>>>>>>>> someone 
>>>>>>>>>>>> could point me in the right direction.  I've attached a screenshot 
>>>>>>>>>>>> of the 
>>>>>>>>>>>> queries for the dashboard and my generator.yml so you can see if I 
>>>>>>>>>>>> have 
>>>>>>>>>>>> this set up correctly.
>>>>>>>>>>>>
>>>>>>>>>>>> ---
>>>>>>>>>>>> auths:
>>>>>>>>>>>>   public_v1:
>>>>>>>>>>>>     version: 1
>>>>>>>>>>>>   public_v2:
>>>>>>>>>>>>     version: 2
>>>>>>>>>>>>
>>>>>>>>>>>> modules:
>>>>>>>>>>>>   # Default IF-MIB interfaces table with ifIndex.
>>>>>>>>>>>>   if_mib:
>>>>>>>>>>>>     walk: [sysUpTime, 1.3.6.1.2.1.2.2, 1.3.6.1.2.1.31.1.1]
>>>>>>>>>>>>     lookups:
>>>>>>>>>>>>       - source_indexes: [ifIndex]
>>>>>>>>>>>>         lookup: ifAlias
>>>>>>>>>>>>       - source_indexes: [ifIndex]
>>>>>>>>>>>>         # Uis OID to avoid conflict with PaloAlto 
>>>>>>>>>>>> PAN-COMMON-MIB.
>>>>>>>>>>>>         lookup: 1.3.6.1.2.1.2.2.1.2 # ifDescr
>>>>>>>>>>>>       - source_indexes: [ifIndex]
>>>>>>>>>>>>         # Use OID to avoid conflict with Netscaler NS-ROOT-MIB.
>>>>>>>>>>>>         lookup: 1.3.6.1.2.1.31.1.1.1.1 # ifName
>>>>>>>>>>>>     overrides:
>>>>>>>>>>>>       ifAlias:
>>>>>>>>>>>>         ignore: true # Lookup metric
>>>>>>>>>>>>       ifDescr:
>>>>>>>>>>>>         ignore: true # Lookup metric
>>>>>>>>>>>>       ifName:
>>>>>>>>>>>>         ignore: true # Lookup metric
>>>>>>>>>>>>       ifType:
>>>>>>>>>>>>         type: EnumAsInfo
>>>>>>>>>>>>   # Default IP-MIB with ipv4InterfaceTable for example.
>>>>>>>>>>>>   ip_mib:
>>>>>>>>>>>>     walk: [ipv4InterfaceTable]
>>>>>>>>>>>>
>>>>>>>>>>>>   readynas:
>>>>>>>>>>>>     walk:
>>>>>>>>>>>>       - 1.3.6.1.4.1.4526               # Raid/Disks status
>>>>>>>>>>>>
>>>>>>>>>>>> # Synology
>>>>>>>>>>>> #
>>>>>>>>>>>> # Synology MIBs can be found here:
>>>>>>>>>>>> #   http://www.synology.com/support/snmp_mib.php
>>>>>>>>>>>> #   
>>>>>>>>>>>> http://dedl.synology.com/download/Document/MIBGuide/Synology_MIB_File.zip
>>>>>>>>>>>> #
>>>>>>>>>>>> # Tested on RS2414rp+ NAS
>>>>>>>>>>>> #
>>>>>>>>>>>>   synology:
>>>>>>>>>>>>     walk:
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.1       # synoSystem
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.2       # synoDisk
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.3       # synoRaid
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.4       # synoUPS
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.5       # synologyDiskSMART
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.6       # synologyService
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.101     # storageIO
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.102     # spaceIO
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.104     # synologyiSCSILUN
>>>>>>>>>>>>       - 1.3.6.1.4.1.6574.3.1  # raid table
>>>>>>>>>>>>     lookups:
>>>>>>>>>>>>       - source_indexes: [spaceIOIndex]
>>>>>>>>>>>>         lookup: spaceIODevice
>>>>>>>>>>>>         drop_source_indexes: true
>>>>>>>>>>>>       - source_indexes: [storageIOIndex]
>>>>>>>>>>>>         lookup: storageIODevice
>>>>>>>>>>>>         drop_source_indexes: true
>>>>>>>>>>>>       - source_indexes: [serviceInfoIndex]
>>>>>>>>>>>>         lookup: serviceName
>>>>>>>>>>>>         drop_source_indexes: true
>>>>>>>>>>>>       - source_indexes: [diskIndex]
>>>>>>>>>>>>         lookup: diskID
>>>>>>>>>>>>         drop_source_indexes: true
>>>>>>>>>>>>       - source_indexes: [raidIndex]
>>>>>>>>>>>>         lookup: raidName
>>>>>>>>>>>>         drop_source_indexes: true
>>>>>>>>>>>>     overrides:
>>>>>>>>>>>>       diskModel:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       diskSMARTAttrName:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       diskSMARTAttrStatus:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       diskSMARTInfoDevName:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       diskType:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       modelName:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       raidFreeSize:
>>>>>>>>>>>>         type: gauge
>>>>>>>>>>>>       raidName:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       raidTotalSize:
>>>>>>>>>>>>         type: gauge
>>>>>>>>>>>>       serialNumber:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       serviceName:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>       version:
>>>>>>>>>>>>         type: DisplayString
>>>>>>>>>>>>
>>>>>>>>>>>> # UCD-SNMP-MIB
>>>>>>>>>>>> #
>>>>>>>>>>>> # University of California, Davis extensions. Commonly used for 
>>>>>>>>>>>> host
>>>>>>>>>>>> # metrics. For example, Linux-based systems, DD-WRT, Synology,
>>>>>>>>>>>> # Mikrotik, Kemp LoadMaster, etc.
>>>>>>>>>>>> #
>>>>>>>>>>>> # http://www.net-snmp.org/docs/mibs/UCD-SNMP-MIB.txt
>>>>>>>>>>>> #
>>>>>>>>>>>>   ucd_la_table:
>>>>>>>>>>>>     walk:
>>>>>>>>>>>>       - 1.3.6.1.4.1.2021.10.1.2 # laNames
>>>>>>>>>>>>       - 1.3.6.1.4.1.2021.10.1.5 # laLoadInt
>>>>>>>>>>>>       - 1.3.6.1.4.1.2021.10.1.6 # laLoadFloat
>>>>>>>>>>>>     lookups:
>>>>>>>>>>>>       - source_indexes: [laIndex]
>>>>>>>>>>>>         lookup: laNames
>>>>>>>>>>>>         drop_source_indexes: true
>>>>>>>>>>>>   ucd_memory:
>>>>>>>>>>>>     walk:
>>>>>>>>>>>>       - 1.3.6.1.4.1.2021.4 # memory
>>>>>>>>>>>>   ucd_system_stats:
>>>>>>>>>>>>     walk:
>>>>>>>>>>>>       - 1.3.6.1.4.1.2021.11 # systemStats
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Any help would be greatly appreciated!
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> [image: Grafana Dashboard NAS.png]
>>>>>>>>>>>>
>>>>>>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/94feca6b-5a3b-4906-b2ec-3794aaaab178n%40googlegroups.com.

Reply via email to