| Subject: |
RE: No data collect after interface down/up |
| Author: |
Jane Curry |
| Posted: |
2017-05-18 11:23 |
Don't understand that one at all. Changing the config of one device should not affect the monitoring of others unless, somehow, they are "behind" that machine in a network sense? Also, when the device comes back, monitoring should resume.
Have you ever seen monitoring graphs from these devices?
Have the interfaces modeled correctly? ie. when you navigate to the device, do you see an interfaces component menu on the left-hand side and then individual interfaces in the main part of the window?
Cheers,
Jane
------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------
| Subject: |
RE: No data collect after interface down/up |
| Author: |
Eirisdg |
| Posted: |
2017-05-19 02:50 |
Sorry, very bad explained.
I thought that the test I did turning down and up the eth interface could be the trouble, but now I think that there is no relation.
The problem is that in all the device class /Server/SSH/Linux, the graphs of monitored elements in the devices of this class shows "no data available", and the graphs are empty with N/A values.
I think I could be caused by a bad threshold applied to the class, already deleted, but I've restarted all the services with no result.
When I see the response of the api petition, has no result.
And yes, yesterday the graphs worked well. And in the other device class, works well too.
What could be the problem?
Thanks
------------------------------
Adrian
------------------------------
| Subject: |
RE: No data collect after interface down/up |
| Author: |
Andrew Kirch |
| Posted: |
2017-05-19 13:36 |
what type of devices are these/ Can you paste the output of zenmodeler -v10 run -d <device>
------------------------------
Andrew Kirch
Senior Solutions Engineer
GoVanguard
------------------------------
