Disk capacity planning for historical data

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.

The table in this chapter provides the following information required to calculate disk space for this monitoring agent:

Table is the table name as it is displayed in the warehouse database, if the attribute group is configured to be written to the warehouse. The table name listed here corresponds to the Table name in Attribute groups and attributes for the Blue Medora Agent for Tivoli Directory Server
Attribute group is the name of the attribute group used to create the table in the warehouse database if it is short enough to fit in the table naming constraints of the database being used for the warehouse. The attribute group name listed here corresponds to the Warehouse table name in Attribute groups and attributes for the Blue Medora Agent for Tivoli Directory Server.
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.
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.
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.

In addition to the information in the tables, you must know the number of instances of data that you plan to collect. An attribute group can have single or multiple instances of data depending on the application environment that is being monitored. For example, if your attribute group is monitoring each processor in your computer and you have a dual processor computer, the number of instances is two.

The following table contains capacity planning information for the data logged by Blue Medora Agent for Tivoli Directory Server.

Table 1. Capacity planning for historical data logged by component Blue Medora Monitoring Agent for IBM Tivoli Directory Server
Table	Attribute group	Bytes per instance (agent)	Database bytes per instance (warehouse)	Aggregate bytes per instance (warehouse)
KB1DPLOG	`KB1_AGENT_DATA_PROVIDER_LOG`	1646	1655	1692
KB1AVAIL	`KB1_AVAILABILITY`	3272	3296	3606
KB1CONFIG	`KB1_CONFIGURATION`	608	635	672
KB1FEATURE	`KB1_FEATURES`	341	339	376
KB1LGDIRAD	`KB1_IBMDIRADM_LOG`	1147	1152	1189
KB1LGSLAPD	`KB1_IBMSLAPD_LOG`	1147	1152	1189
KB1SLMON	`KB1_MONITOR`	1038	1157	3786
KB1CONTEXT	`KB1_NAMING_CONTEXTS`	331	328	365
KB1POBJST	`KB1_PERFORMANCE_OBJECT_STATUS`	352	399	664
KB1REACH	`KB1_REACHABLE`	80	77	114
KB1REPLICA	`KB1_REPLICATION`	1079	1085	1200
KB1SERVER	`KB1_SERVER_INFORMATION`	565	567	604
KB1VERSION	`KB1_SUPPORTED_LDAP_VERSION`	80	77	114
KB1SYSMON	`KB1_SYSTEM_MONITOR`	292	293	486
KB1THPLST	`KB1_THREAD_POOL_STATUS`	124	168	550

For more information about historical data collection, see the IBM Tivoli Monitoring Administrator's Guide.