Disk capacity planning for a monitoring agent is a prediction of the amount of disk space to be consumed for each attribute group whose historical data is being collected. Required disk storage is an important factor to consider when you are defining data collection rules and your strategy for historical data collection.
Expected number of instances is a guideline that can be different for each attribute group, because it is the number of instances of data that the agent will return for a given attribute group, and depends on the application environment that is being monitored. For example, if your attribute group is monitoring each processor on your machine and you have a dual processor machine, the number of instances is 2.
Calculate expected disk space consumption by multiplying the number of bytes per instance by the expected number of instances, and then multiplying that product by the number of samples.Table 2 provides the following information required to calculate disk space for the Monitoring Agent for Windows OS:
v Bytes per instance (agent) is an estimate of the record length for each row or instance written to the agent disk for historical data collection. This estimate can be used for agent disk space planning purposes.
v Database bytes per instance (warehouse) is an estimate of the record length for detailed records written to the warehouse database, if the attribute group is configured to be written to the warehouse. Detailed records are those that have been uploaded from the agent for long-term historical data collection. This estimate can be used for warehouse disk space planning purposes.
v Aggregate bytes per instance (warehouse) is an estimate of the record length for aggregate records written to the warehouse database, if the attribute group is configured to be written to the warehouse.
Aggregate records are created by the Summarization agent for attribute groups that have been
configured for summarization. This estimate can be used for warehouse disk space planning purposes.
The IBM Tivoli Monitoring Installation and Setup Guide contains formulas that can be used to estimate the amount of disk space used at the agent and in the warehouse database for historical data collection of an attribute group.
Table 2. Capacity planning for historical data logged by component
Table Attribute group
Table 2. Capacity planning for historical data logged by component (continued)
Table 2. Capacity planning for historical data logged by component (continued)
Table Attribute group
Bytes per instance (agent)
Database bytes per instance (warehouse)
Aggregate bytes per instance (warehouse)
NTSVCDEP NT_Service_Dependencies 708 704 741
NTSERVICE NT_Services 1496 1507 1544
WTSYSTEM NT_System 924 824 1788
WTTHREAD NT_Thread 356 229 515
NETWRKIN Network_Interface 504 516 1174
NETSEGMT Network_Segment 208 204 514
PRINTQ Print_Queue 604 617 1129
PROCESSIO Process_IO 732 607 956
KNTRASPT RAS_Port 248 254 714
KNTRASTOT RAS_Total 316 194 669
SMTPSRV SMTP_Server 396 439 2006
TCPSTATS TCP_Statistics 280 149 441
UDPSTATS UDP_Statistics 264 129 337
VMMEMORY VM_Memory 156 164 669
VMPROCSSR VM_Processor 200 204 514
WEBSVC Web_Service 420 466 2015
For more information about historical data collection, see the IBM Tivoli Monitoring Administrator's Guide.
Chapter 3. Situations
A situation is a logical expression involving one or more system conditions. Situations are used to monitor the condition of systems in your network. You can manage situations from the Tivoli Enterprise Portal by using the situation editor.
The IBM Tivoli Monitoring agents that you use to monitor your system environment are shipped with a set of predefined situations that you can use as-is or you can create new situations to meet your
requirements. Predefined situations contain attributes that check for system conditions common to many enterprises.
Using predefined situations can improve the speed with which you can begin using Monitoring Agent for Windows OS. You can examine and, if necessary, change the conditions or values being monitored by a predefined situation to those best suited to your enterprise.
Note: The predefined situations provided with this monitoring agent are not read-only. Do not edit these situations and save over them. Software updates will write over any of the changes that you make to these situations. Instead, copy the situations that you want to change to suit your enterprise.
In some cases, the values assigned to the predefined situations are examples only and must be modified to reflect the conditions of your distributed system.
You can display predefined situations and create your own situations using the Situation editor. The left frame of the Situation editor initially lists the situations associated with the Navigator item that you selected. When you click a situation name or create a new situation, the right frame opens with the following tabs:
Formula
Condition being tested Distribution
List of managed systems (operating systems, subsystems, or applications) to which the situation can be distributed.
Expert Advice
Comments and instructions to be read in the event workspace Action
Command to be sent to the system Until Duration of the situation
EIF Whether to send a Tivoli Enterprise Console®event and event severity
IBM Tivoli Monitoring for Windows includes the following types of predefined situations:
Automatically installed and activated at startup
These situations are automatically installed, distributed, assigned to a managed object, and started.
Not automatically installed but activated at startup
These situations are not automatically installed, distributed, assigned to a managed object, but once they are installed, they are automatically started.
Automatically installed and not activated at startup
These situations are automatically installed when you install the Tivoli Enterprise Portal Server.
However, they must be distributed, added to a managed object, and started.
Bottleneck analysis, not activated at startup
These situations are designed specifically to help you to isolate areas of your system that are contributing to bottleneck conditions. These situations are not activated at startup.
The IBM Tivoli Monitoring User's Guide contains more information about predefined and custom situations and how to use them to respond to alerts.