Viewing analytics
To see the Analytics page, open the Events menu and select Analytics.

Item | Feature | Description | |
|---|---|---|---|
1 | Date range | This is the date range for the data currently displayed. By default, the Analytics page shows data for the last three months. Click the dates to select a different date range. | |
2 | Refresh button | Click | |
3 | Exceptions | Total numbers of exceptions and events that occurred during the selected date range. | |
4 | Total Events | Number of total events | |
5 | Events Detected On | Total number of Db2 data sharing groups, Db2 subsystems, LPARs, or IMS that had detected events during the selected date range. | |
6
| Events per day | Bar graph showing the number of events and Exceptions per day during the selected date range Each type of event is displayed in a different color. Days with no events are not displayed on the graph. Hover over the bar graph to see the numbers for events or Exceptions on that day. | |
7 | DSG / Db2 Subsystem / LPAR Events/ IMS | List of Db2 data sharing groups, Db2 subsystems, LPARs, and IMS systems that experienced events within the selected date range, along with the number of events affecting each Db2 data sharing group, subsystem, or IMS system. Click the number of events for a Db2 data sharing group, Db2 subsystem, LPAR, or IMS system to see which KPI groups were impacted by the events, and how many events impacted each KPI Group.
| |
8 | Event breakup by KPI Group | List of KPI Groups that had events during the date range and the number of events that impacted the KPI Group Click the number of events for a KPI Group to see which Db2 data sharing groups, Db2 subsystems, LPARs, and IMS systems were impacted by the events, and how many events impacted each Db2 data sharing group, Db2 subsystem, or IMS system.
| |
9 | Top 10 - Events by duration | The 10 events that persisted for the longest amount of time during the selected date range The start time of events is calculated according to the local time zone of the Db2 or IMS. Events that are ongoing at the time of data aggregation are indicated by an asterisk (*). | |

