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/

Reply via email to