|
| | | Junior Member
 
Group: Forum Members
Last Login: 12/17/2005 2:55:00 PM
Posts: 12, Visits: 1 |
| I'm trying to figure out how to fix two issues we're having with performance polling of ping data.
1. Since there isn't a way to enable it globally (yet), I enabled polling for all devices via SQL. Many of the devices started polling and reporting performance data, but I also still have quite a few devices reporting "Samples Still Being Collected" when trying to view performance data. It's been in that state for almost a day now. Any ideas on how to get it working?
2. Is there any way to make the performance graphs scale better so you can see the granularity in the data? All of the ping performance graphs don't really show much since the times are all hovering < .1.
Thanks to anyone for their help. |
| |
| | | 
Time Traveler
Group: WhatsUp Gold Expert
Last Login: Today @ 1:49:13 PM
Posts: 1,513, Visits: 5,018 |
| Hi,
Issue 1 : Although you can enable performance gathering for all monitors, data is collected ONLY for the ping monitor. This might be the reason why you see this message. I discussed that with Ipswitch and they confirmed it. They said it was because they were afraid of collecting too much data for the 2GB msde... A pity. I hope and think it will change in the future 'cause ping performance is rarely useful.
Issue 2 : Tricky one. You can try and edit the ASP page that runs the report. It uses a graphing COM component that comes with WUP. It's probably possible to change the scale -and other stuff as well. Edit ASP at your own risk 'cause with updates Ipswitch will probably -and it is normal- overwrite your edits.
HTH
Reading, writing and arithmetic - If you need to choose, please take option 1. |
| |
| | | Supreme Being
Group: Forum Members
Last Login: 7/24/2005 6:18:00 AM
Posts: 117, Visits: 1 |
| You also need to keep in mind that when you add or modify a device using the WUP console that is communicating with the polling engine, it somehow has a way of notifying the polling engine when a new device has been added or when polling has been turned on for a device that previously wasn't being polled. If you change the properties of a given device OUTSIDE of the WUP console (say, manually with SQL) or you try to enable monitors for a device through a WUP console that isn't on the same machine that is doing the polling, then the polling engine has no idea that there is a new device for it to poll. The quickest and easiest way I've found to correct this situation is to restart the Ipswitch WhatsUp Engine service (NmService.exe). It seems that the polling engine notices these new devices upon startup. I've noticed that other techniques can also cause the polling engine to suddenly become "aware" of the new devices or monitors, such as adding a new device using the WUP console to the same map as the device that was modified with SQL. But if you have gone through your entire database with SQL and modified a bunch of different devices across a bunch of different groups, the easiest way is to just restart WUP. -- Nathan |
| |
|
|