User Guide

Chapter 13 Performance Tips
Exit AlarmTracker When You Are Not On the Job
13-6
Cisco AlarmTracker Client User Guide
OL-1501-01
raised and cleared. You would see this as a set of bars that go across horizontally
in this view. The more time history you have, the more likely it is that you will be
able to see this type of phenomenon.
The disadvantage, of course, is that it takes more time to perform each query, more
time to transfer the data across the wire to your AlarmTracker client machine, and
more time to fill up the display.
If you want to optimize performance, set this value to 1 hour. This means you are
only returning Alarm and Event data for closed Alarm objects whose closed time
is less than one hour ago. This minimizes the data sent across the wire.
Exit AlarmTracker When You Are Not On the Job
When you leave at the end of your shift, exit AlarmTracker. When AlarmTracker
is running you are receiving a constant stream of Listener data from LGMapper.
This consumes resources in the LGMapper server that are dedicated to your
connection, and it uses network bandwidth. For example, for a TAC that supports
150 Customers, approximately 34kBytes of data are sent across the wire to your
AlarmTracker client every minute. By exiting the AlarmTracker application when
you are not using it, you will reduce the amount of network traffic, and reduce the
load on the LGMapper server.
Select Only the Customers and Products You Need
To Monitor
If you know that you are responsible for only a subset of the customers or
products, you can select a subset of the full list to monitor. Use the Tools > Filter
dialog.