The issue that WhatsUp Gold might behave ungracefully when viewing large logs is something that is being looked at.
My suggestion concerning configuration of specific events was a work-around for the lock-up issue - but, hopefully, it would out you more in control of things: 1 trap a second is a LOT to have to deal with if you don't use specific events to do it for you. The "Filter Out All Unsolicited Traps" feature is something that might typically enable when you are satisfied that all the interesting traps that will be received are accounted for by events that are configured on the appropriate devices. That is, you leave things unfiltered whilst you observe and tweak. Once the filter is turned on then traps that do not fire events will not appear in the Activity Log. And the same applies to Syslog (to answer your other question). I have entered the purge suggestion as a feature request. Personally, I do believe that Perl would still do a better job because that's exactly the sort of thing that Perl is best at. As for the issue of things that can only be configured via the console and not the web... I know exactly what you mean. It is an issue that we are aware of. Mark Symons Ipswitch, Inc Augusta GA -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Adamson, Bob E Sent: Thursday, March 27, 2003 20:31 To: [EMAIL PROTECTED] Subject: RE: [WhatsUp Forum] Viewing Log locks up What's Up Gold Of course we can configure the devices to be somewhat less talkative, and actually I got one of our server folk to take care of this today. One of my questions however is "what if we don't want to?" In the event that this is information that we want available, WUG appears to be unable to deal with the large volume of information. This is typical in situations where an application makes use of text files to store information. If there was instead a database backend, SQL for example, you would see the application better able to deal with these more verbose environments or those that require long-term logging to be in place. Additionally, you are correct in that we could implement a perl script to automatically parse through and eliminate records from the *.tab files. The only issue I have with this is that there is no reason why WUG should not be able to do this natively. The code should be fairly trivial to implement a button that is a "Purge Logs" for a particular device and I for one would find this to be a very useful addition. Could you better explain the "Filter Out All Unsolicited Traps" feature? I have seen the option, I have read the brief piece of documentation about what it does, and don't truly have my mind wrapped around what happens if I enable this. In the case of a syslog message, does it not appear in the Event Log unless there is an event associated with it but still shows up in the syslog log if this option is enabled? Does this carry over to the log view in the web interface as well? Finally, to get totally off topic, I hate having to stop the service to enable the application to do most of my configuration, and then go back to the service for ongoing, normal duty. Ideally, I would like to be able to do everything from the web interface only. However, as I can see some of the challenges involved in manipulating map items from a web browser among other things, what about coming up with a way to run the service all the time and still be able to run the application to do configurations? If all I had to do was stop and restart the service to enable changes, my life would be a happier one. Now, given all of this, I do want to say that I have been using WUG since version 4. I believe that it is far and away the best value on the market and am continually amazed at what can be done with it for the price. I have seen many HP Openview and CA Unicenter implementations fail for many reasons, usually because people don't understand the amount of work that goes into setting these systems up and maintaining them. WUG has remained easy to implement and maintain in a basic form for most environments even as the feature set has increased. I want to commend you all for a job well done. Thanks, Bob -----Original Message----- From: Mark Symons [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 3:30 PM To: [EMAIL PROTECTED] Subject: RE: [WhatsUp Forum] Viewing Log locks up What's Up Gold Is it not possible to configure the sending devices so that they are a little more discriminating in what they transmit? On the WhatsUp Gold side... I would suggest configuring the devices on your maps so that they have the specific events that are of interest to you, and then configuring the SNMP Event server so that "Filter Out All Unsolicited Traps" is enabled. Thus, you might still receive 1 trap per second but only fire 1 Event per hour. Now, the SNMP log will still show 1 entry per second... but it's the Activity Log that records Events, and the Activity Log that gets displayed in Quick Status. This should help with your locking up problem by ensuring that you are working with smaller log files. It also should be possible to manipulate your EV log files using a third-party application whilst WhatsUp Gold is running. I do this manually all the time using my favorite Text editor. Perhaps something in Perl (as MRTG is already running)? We have previously logged a feature request for the log viewers to offer various filtering options, and for logging itself to have some sort of filtering (don't log things that we know from experience are not of interest). Mark Symons Ipswitch, Inc Augusta GA -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Adamson, Bob E Sent: Thursday, March 27, 2003 11:16 To: [EMAIL PROTECTED] Subject: RE: [WhatsUp Forum] Viewing Log locks up What's Up Gold Greetings, I am seeing a similar issue but have been able to track it down to issues with the sheer size of some of our log files. I have found that we have a Citrix server farm that is generating a huge number of SNMP traps, well over one per second, that is resulting in log files that are larger than 70megs on some weeks. If I allow these log files to continue to exist, then WUG will first cease sending the downtime reports (I assume because it can't parse the log files quickly enough) and then ultimately the CPU will peg and the application will need to be killed. This occurs whether running as an application or as a service. I have seen similar issues when using the Quick Status out of the application. Again, the application is attempting to parse the logs to display them for just that device and is getting hung up. I would like to see, unless it is already there and I am truly blind, an option to purge a particular device's logs from the log files. I can simply go into the file after stopping the application and manually purge these but quite frankly I just want a button to accomplish this from both the web interface as well as the application interface. FYI, I have WUG sitting on a Compaq DL380 with dual P3-933s and 2GB of RAM running Windows 2000 server. The only other applications being run on this server are MRTG and IIS and I can clearly see the minimal amount of resources that this is consuming. Bob -----Original Message----- From: brandon.baker [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 7:53 AM To: '[EMAIL PROTECTED]' Subject: RE: [WhatsUp Forum] Viewing Log locks up What's Up Gold I had them problem in both version. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 10:40 AM To: [EMAIL PROTECTED] Subject: [WhatsUp Forum] Viewing Log locks up What's Up Gold Has anyone experienced What's Up Gold locking up when you right click a device choose quick status and then try to show the log. As soon as I select the log What's Up Gold immediately stops responding and won't recover. I am running Ver. 8.0 I never had this happen in ver 7. Thanks, Matt Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
