Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Synology targets down snmp_exporter #614

Open
davidepellegrini opened this issue Feb 15, 2021 · 4 comments
Open

Synology targets down snmp_exporter #614

davidepellegrini opened this issue Feb 15, 2021 · 4 comments

Comments

@davidepellegrini
Copy link

davidepellegrini commented Feb 15, 2021

Host operating system: uname -a

Linux "hostname" 3.10.0-1062.1.1.el7.x86_64 #1 SMP Fri Sep 13 22:55:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

snmp_exporter version: output of snmp_exporter -version

What device/snmpwalk OID are you using?

Synology MIB

If this is a new device, please link to the MIB(s).

It's not a new device, i already monitoring this synologys before.
https://global.download.synology.com/download/Document/Software/DeveloperGuide/Firmware/DSM/All/enu/Synology_MIB_File.zip

What did you do that produced an error?

I don't change settings, and i have this issue, this is my prometheus config file about synology:

  • job_name: 'snmp-exporter-synology'
    honor_timestamps: true
    scrape_interval: 10m
    scrape_timeout: 60s
    static_configs:
    • targets: # SNMP devices
      • 10.1.1.5
      • 10.1.1.20
      • 10.4.0.2
        #- 10.0.1.4
        #- 10.0.1.3
        #- 10.0.1.5
        metrics_path: /snmp
        params:
        module: [synology]
        relabel_configs:
    • source_labels: [address]
      target_label: __param_target
    • source_labels: [__param_target]
      target_label: instance
    • target_label: address
      replacement: 10.0.1.241:9116 # The SNMP exporter's real hostname:port.

What did you expect to see?

My targets up and alerts on, like it was a few months ago

What did you see instead?

image

@SuperQ
Copy link
Member

SuperQ commented Feb 15, 2021

For questions/help/support please use our community channels. There are more people available to potentially respond to your request and the whole community can benefit from the answers provided.

@cdalvaro
Copy link

@davidepellegrini, did you figure out how to solve this issue?

@cdalvaro
Copy link

I managed to fix this issue by setting network_mode: host on my docker-compose file for the snmp-exporter service.

@davidepellegrini
Copy link
Author

@cdalvaro I have fixed this issue by change the scrape interval from 60 seconds to 120 seconds. I will try your suggestion too, thanks for your reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants