search

WaterByWind / grafana-dashboards

Grafana Dashboards
MIT License
293 stars 53 forks source link

Edgerouter lite #9

Open nheinemans opened 7 years ago

nheinemans commented 7 years ago

Hi,

After starting telegraf with your configuration and mibs, I get these error messages: 2017-06-15T13:56:16Z E! Error in plugin [inputs.snmp]: agent 192.168.1.1: gathering table ifXTable: performing bulk walk for field ifConnectorPresent: Request timeout (after 3 retries) 2017-06-15T13:56:26Z E! Error in plugin [inputs.snmp]: agent 192.168.1.1: gathering table ipSystemStatsTable: performing bulk walk for field ipSystemStatsInReceives: Request timeout (after 3 retries)

The grafana dashboard shows most metrics, however both Interface Traffic graphs are empty.

Any idea what might be causing this?

sjabby commented 7 years ago

Same issue here.

WaterByWind commented 7 years ago

Is this repeating continually for both of you?

This would suggest that the ER is taking too long to respond to the SNMP query but it is odd that it would only happen with these.

Which version of telegraf are you using ('telegraf version' would show this)?

Which model of ER are you monitoring?

sjabby commented 7 years ago

Telegraf 1.3.1 and 1.3.4 same issue. ERPOE5 for me

nheinemans commented 7 years ago

Telegraf 1.3.4, EdgeRouter Lite running EdgeOS 1.9.0.

tjend commented 7 years ago

I set to the timeout to 10 seconds to avoid this issue.

repvik commented 6 years ago

Fails even with a 50s timeout for me. ERPOE-5, Telegraf 1.5.1:

2018-01-30T18:15:27Z E! Error in plugin [inputs.snmp]: agent 192.168.10.1: gathering table ifXTable: performing bulk walk for field ifCounterDiscontinuityTime: Request timeout (after 3 retries)

repvik commented 6 years ago

Reduced max_repetitions to the standard 20, now I get no errors with a 5s timeout.

repvik commented 6 years ago

Interfaces do not show up in telegraf however.

show measurements name: measurements name

cpu disk diskio kernel mem processes swap system

burkasaurusrex commented 6 years ago

Just came here to say I'm having the same issue, with an ER-PoE-5, firmware v1.10.1. It appears as though extending the timeout to 10s has fixed things for now.

tstackhouse commented 6 years ago

I'm having this issue on an ER-X running v1.9.7+hotfix.3 after updating to the latest telegraf (1.6.1), no matter how high I set the timeout (up to 50s) or how low I make max_repetitions (as low as 10).

Update: This seems to go away if I reboot the router, I wonder if there is an issue in the firmware. I reverted to 10s/25 in my config. Will continue to monitor the situation.

samip5 commented 5 years ago

Yup. does not work on ER-X with firmware 2.0.6.