The Statistics Reporting template is a special template used to automatically create a database that records and stores information about one or more Notes servers. The database then serves as a repository for information about server usage, resources, alarms, and events. You can view this information graphically in the database, and even export it to a spreadsheet for creating more formal reports.
You can create a Statistics Reporting database for each Notes server, or for all of the servers within a particular domain. Each server automatically records its own statistics in the database, based on a frequency that you determine (the interval can be as small as 15 minutes, or as large as you wish).
You may choose to create an accompanying Alarm Tracking database and forward the alarms recorded in this database to the Alarm Tracking database.
For more information on setting up the Statistics Reporting database, see the Lotus Notes
Administrator's Guide.
To the Server Administrator/Database Manager:
Access Control List
. The Access Control List (ACL) is set up so that by default, the server is defined as manager. Immediately after the Statistics Reporting database is created, the server administrator should change the ACL to make himself or herself manager of the database.
The default access is Reader.
The administrator maintains the ACL. He or she may change the default access or add additional managers.
About Statistics Reporting
You are looking at it now. Read (and maybe print) this information. Replace the current contents with a paragraph or two that explains the purpose of this database, its audience, and how to contact the database manager(s).
(To edit the About Database document, select Design, Help Document, About Database.)
Using Statistics Reporting
Be sure to update the Using Database document. It should give users specific information on the use of the database.
(To edit the Using Database document, select Design, Help Document, Using Database.)
This database contains statistics on one or more Notes servers within this domain.
Statistics reported include:
Alarms (you define the conditions that trigger each type of alarm)
Events and their severity levels (you define the severity levels for each type of event)
Server usage levelsa
Server resources
For recommendations on using this database in conjunction with the Alarm Tracking database, see the Lotus Notes Administrator's Guide.
Note: This database works in conjunction with an external database called EVTTYPES.NMF. You will receive errors if you try to use this database without the presence of the EVTTYPES
database, which is usually installed only on servers.
If you are at your workstation and are using Server-based mail, Notes looks for the EVTTYPES database on your home server. Otherwise, it looks for the database on your local workstation.
Types of Documents
This database is intended to be used as a repository for server statistics; it receives its data automatically from the Notes servers. The only type of document that you can compose is the Trouble Ticket, described below.
Alarm/Event Trouble Ticket
use these forms to forward alarm reports 9
or events
to the Alarm Tracking database (ALRMTRAK.NSF). Highlight the alarm to be forwarded, and choose l
Compose, *
Alarm
Trouble Ticket
Compose, Event Trouble Ticket
. Fill in any additional information if necessary,
then select the
Dispatch Ticket
button to send the Trouble Ticket to the Alarm Tracking database.
Views and FoldersT
Alarms
Records alarms are triggered by the conditions specified in the Server Admin. Threshold record for each server (the records are stored in the Name & Address Book). The alarms are sorted by server; each alarm record indicates the number of occurrences of that alarm. You can send the alarms to the Alarm Tracking database by choosing Compose, Alarm Trouble Ticket and filling in the appropriate information, then selecting the
Dispatch Ticket
button.
Events
Records events along with their time of occurrence and severity level (Fatal, Failure, Normal, Warning High, or Warning Low). Event records are sorted by server. You probably won't want to track "Normal" events due to the high volume of records that will be stored. For information on tracking events, see the
Administrator's Guide.
You can
send
the events to the Alarm Tracking database by choosing Compose,
Event
Trouble Ticket and filling in the appropriate information, then selecting the
Dispatch Ticket
button.
Graphs Only
Displays the statistics as a graph, plotted over time and sorted by server. You can visually track usage for disk space, swap files, memory,
users, and transactions per minute
Load Graphs#
Graphically tracks the user load for each server at different times of the day, indicating the number of transactions per minute, the number of users logged on, and the size of the swap file.
Resource Graphs
Shows the level of resource usage (disk space
memory
) over time, sorted by server.
Spreadsheet Export
Displays the recorded statistics in a form that you can easily export to a spreadsheet such as Lotus 1-2-3 for Windows, for storage and for use in more formal reporting. You should redesign this view to meet your own needs (see the
Application Developer's Reference
for instructions on designing a view). For information on exporting the view to a spreadsheet, see Notes online
Help.
Statistics Reports
Records the load and resource statistics for each server at different times of day. Statistics recorded include: disk space usage, memory allocations, swap file size, threads, users, transactions per minute, dead mail, and pending mail. This information is used to create the graphical and spreadsheet views described below.
(.txt)