One thought, maybe there's an open file descriptor limit on the
snmp_exporter that's being hit?
On Thu, Aug 13, 2020 at 5:18 PM Ben Kochie wrote:
> It looks like the error is coming from the SNMP implementation, when
> trying to use a standard net Dialer.
>
>
> https://github.com/soniah/gosnmp/b
It looks like the error is coming from the SNMP implementation, when trying
to use a standard net Dialer.
https://github.com/soniah/gosnmp/blob/cce23a3123384acf2aebdee032c5ef38698fe290/gosnmp.go#L255-L258
If my understanding of the code is correct, this should be using a normal
Golang DNS resolve
boilerplate..
- job_name: 'protocols'
file_sd_configs:
- files:
- protocols_targets.json
metrics_path: /snmp
params:
module: [protocols]
relabel_configs:
- source_labels: [__address__]
target_label: __param_target
- source_labels: [__param_target]
target_label: instance
- target_label: __address__
Yes, that looks like a DNS issue to me.
What is the prometheus.yml configuration for this?
On Thu, Aug 13, 2020 at 3:08 PM dari...@gmail.com
wrote:
> Hello,
>
> I have snmp exporter with various network devices, which works fine most
> of the time. However, sometime I notice false alerts and wh
Hello,
I have snmp exporter with various network devices, which works fine most of
the time. However, sometime I notice false alerts and when I look at the
job, there are gaps of. which snmp exporter doesn't register this as 0, its
just a gap. When looking at snmp exporter logs I noticed these
5 matches
Mail list logo
