IBM Tivoli Monitoring, Version 6.3

Managed System Status workspace

The Managed System Status workspace is one of the predefined workspaces for the Enterprise Navigator item, and offers a high level overview of your managed network. The workspace has a single view: Managed System Status table view.

Accessing the workspace

To open the Managed System Status workspace, take the following steps:
  1. Click the Enterprise Navigator item to open its default workspace.
  2. Click Workspace gallery Workspace gallery, then click the thumbnail graphic for Managed System Status.

What the workspace shows

The Managed System Status table view is a list of monitoring agents in your managed network. The Status column reports the ONLINE or OFFLINE status of the agent, with offline agents shown first.

An agent that has actually been removed from the monitored environment might appear to be offline. You can remove the display of the offline agent from the view and from the Navigator by right-clicking the table row and clicking Clear offline entry.

The CQ agent might be displayed in the table results. The CQ agent is a monitoring agent for the portal server and is not the actual portal server component. The status of this agent does not correlate to the status of the actual portal server. If this agent displays an offline status, there might have been a problem starting the agent or the monitoring server might not have completed refreshing.

Links to the Audit Log workspace, Agent Operations Log workspace, and Historical Export Statistics workspace
Right-click the link at the beginning of a row to select what log workspace you want to view. The log workspace is filtered to show only the messages that have been logged for the selected managed system.
Tip: If you click the link (instead of a right-click), the agent operations log is displayed by default. You must right-click in order to see the Audit Log or History Exports options.
Here is an example of a link from the hub monitoring server row:
This example displays a subset of the targeted Agent Operations Log linked workspace:
This example displays a subset of the targeted Audit Log linked workspace:
This example displays a subset of the targeted History Exports linked workspace:

Audit Log workspace

The Audit Log workspace displays audit events for self-describing agent related events, Warehouse Proxy Agent events, Tivoli® Application Dependency Discovery Manager integration events, stop events, and start events. Audit records are stored in two formats. Audit records are stored as pure events in the ITM Audit attribute group and also in an XML formatted audit.log.

The Audit Log workspace displays the audit records stored in the ITM Audit attribute table. You can collect data from this table historically in the IBM® Tivoli Monitoring warehouse. You may also define situations to monitor the data in this table.

Tip: To quickly assess errors, look under the Result column for row entries with non-zero values (0 indicates a success, so any other value indicates an error). Then look at the information in the other columns to further research the error.
The audit data is normalized and based on the IBM W7 language and collected in the Audit Log table and stored in an XML format on distributed systems and in the SMF facility on z/OS. Each audit data event record answers the following questions:
Questions Key attributes
Who: The user, application, or process that initiated the event Authorization ID, Entity, RunAs, System Name, User ID
What: The type of action the event represents See the Operation attributes
When: The time the event occurred Timestamp
On What: The database, application, file, or permission that was manipulated See the Object attributes
Where: The machine that the event occurred See the Origin attributes
Where from: The system that is the source of the event See the Source attributes
Where to: The targeted system of the event See the Target attributes
Results: The event status and associated message Resource Bundle Key, Result, Message
By default, the Audit log workspace shows audit records generated since the component was last started. In order to view audit events that occurred before the component was last restarted, you must configure the ITM Audit attribute group to collect historical data. To configure historical collection for the ITM Audit attribute complete the following steps:
  1. Click History Configuration, then select CCC Logs under Monitored Applications.
  2. Configure how long to keep Detailed data for the ITM Audit attribute group available locally.
    1. In the Select Attribute Group section, select ITM Audit.
    2. In the Configuration Controls section under Pruning select Detailed data and specify how long to keep the data.
    3. Click Apply.
  3. Create a History Collection setting for the ITM Audit attribute group.
    1. Right-click CCC Logs under Monitored Applications and select Create new collection settings.
    2. Supply a Name, Description and select the ITM Audit Attribute group.
    3. If you plan to historically collect monitoring server Audit records, on the Basic tab you must specify Collection Location: TEMS.
    4. On the Distribution tab, Distribute to Managed System (Agent) and then select the Managed System Group or systems to start collection on.
    5. Click OK.

Historical Export Statistics workspace

The Historical Export Statistics workspace displays the enterprise and private historical exports to a Warehouse Proxy agent instance performed by a selected managed system. This workspace is available for monitoring servers and monitoring agents.

The statistics include the number of rows exported, the size of each row, the total amount of uncompressed data uploaded, and the timestamps for the start and end of key steps in the export process. This workspace allows you to see what historical collections are currently being exported by the managed system, determine whether or not the exports have been successful, determine the amount of time to complete an export, and determine the amount of data being exported. If the amount of exported data is excessive, you might want to reduce the collection interval for sampled attribute groups.

The historical collection statistics data is stored in the O4SRV.KRAHIST table. Using this table you can create custom queries and situations.

The historical export data for a managed system can be viewed using the agent's service interface. For an autonomous agent, this is the only way to view the historical export statistics data. From the service interface, select service interface request and enter the following:
<REPORT>
<SQLTABLE>
<TABLENAME>KRAHIST</TABLENAME>
</SQLTABLE>
</REPORT>
Usage notes:
  • In order to view the workspace data, the selected managed system must have at minimum an IBM Tivoli Monitoring V6.3 framework or the workspace data will be empty or you might receive a KFWITM217E Request error: SQL1_CreateRequest failed message.
    For example:
    • When viewing a monitoring server's workspace data, the monitoring server must be an IBM Tivoli Monitoring V6.3 monitoring server.
    • When viewing an agent's workspace data, the agent framework used by the agent and the monitoring server it connects to and the hub monitoring server must be IBM Tivoli Monitoring V6.3.
  • The workspace shows the historical collections distributed to the selected managed system, where the collection location in the historical collection is set to store at the agent. If the collection location is set to store at the managing server, the collection is displayed in the Historical Export Statistics workspace for the monitoring server the agent reports to.
  • This workspace is empty if a subnode is selected. The collections are displayed in the subnode's managing system.
  • The collection interval for an attribute group that contains event data is always 0 regardless of what was specified in the historical collection.
  • The warehouse interval for an attribute group that contains event data is always 30 minutes regardless of what was specified in the historical collection.
Parent topic: Managed system status
Related tasks:
Adding a Managed System Status view to a workspace
Related reference:
EIB Change Log workspace
Self-Monitoring Topology workspace

Feedback