Comparing the Availability, MTTR, MTBF, and MTBSI graph data
This example scenario shows sample data for all of the BMC TrueSight Operations Management Reporting Event and Impact reports. It illustrates the way the reports calculate values for a component with fluctuating states and can help administrators validate the data in the calculations that they receive from reports.
This scenario covers the 8-hour period from 12 A.M. to 8 A.M.
At 10 P.M., the component state changed from Unavailable to OK.
At 12 A.M. (the beginning of the reporting period), the example component is in the OK state. At 4 A.M., the administrator puts the component into the Maintenance state to perform a backup, which lasts half an hour. At 4:30 A.M., the administrator takes the component out of the Maintenance state and the component reverts to the OK state.
At 5:45 A.M., a database on which the service model component depends has a problem, and the component state changes to Impacted. At 6 A.M., that database goes down, and the component state changes to Unavailable. The problem is corrected at 6:35 A.M., and the component again enters the OK state.
At 7:50 A.M., a network problem causes the component to change again to Unavailable. The component remains in the Unavailable state past 8 A.M.
The information in the following section contains the data and calculations that appear in each report based on the scenario. Values that represent elapsed time are in milliseconds. Null values indicate that no values exist for that period and no points appear on the graph.
See the following topics for report data examples:
Related topics