The following is contained on this page:
The OCC Alert Reporting is indended as a kind of health check for the OCC. It provides various out-of-the-box key figures that help you to determine the workload for the OCC during a certain time span and whether or not the OCC was able to handle the workload.
The OCC Alert Reporting can be accessed from the Solution Manager Launchpad.
This tile opens a new window for the OCC Alert Reporting. The OCC Alert Reporting can also be accesses from the area System and Application Monitoring in the launchpad.
Content of the OCC Alert Reporting
The screen is structured as follows from top to bottom:
- Tabs: Business Process Operation and Application Operation
- Selection Fields impacting which data is loaded to the frontend
- Pie charts for key figures
- Number of alerts per status
- Number of alerts per alert processor
- Number of confirmed alerts per confirmation type
- Number of alerts per confirming user
- Number of confirmed alerts per confirmaton classification
- Number of confirmed alerts per conformation category
- Filters for Key Figure Tables
- Display options for Key Figure Tables
- Sorting options for Key Figure Tables
- Table charts for key figures:
- Number of alerts
- Number of alert instances
- Maximum duration until alert confirmation (in minutes)
- Average duration until alert confirmation (in minutes)
- Number of confirmed alerts with/without incidents
- Number of alerts with manually created incidents
- Maximum alert response times (in minutes)
- Number of alerts with automatically created incidents
On the right-hand-side of the screen you can access the "Additonal Functions".
In the following, the different sections are explained in detail.
Tabs "BPO Alert Reporting" and "AO Alert Reporting"
OCC Alert Reporting is available for alerts from Technical Monitoring and from Business Process Monitoring. In tab "AO Alert Reporting" information concerning the technical alerts is displayed. In tab "BPO Alert Reporting" information concerning all alerts that have been assigned to a business process is displayed. This may include technical alerts from the shared use cases.
Each tab provides the same key figures. The selection options and filter criteria differ slightly (e.g. to select per business process does not make sense for technical alerts).
On the top of the screen you see the selection fields for all key figures. As mentioned before, the available selection fields differ slightly between the two different tabs.
(click picture to enlarge)
The selection criteria (except the drill down parameters) are persisted per user and can be overwritten by adding specific parameters to the URL.
Initially the data are loaded on every selection criteria change. This can be avoided by setting the refresh option to manual. Then the data will be loaded by pressing the button "Apply". Alternatively the screen can be refreshed with the current selection parameters frequently after a specific time.
General Selection Criteria
- Alert Creation Date Range - Time span for the alert creation. Use the pre-defined time spans. You can also use a free date selection (see the chapter "Advanced Usage").
- Data Source - The data can be loaded from the Alert Store (just-in-time reporting) or the Business Warehouse (in case the reporting timeframe exceeds the lifetime of the alerts in the alert store).
Selection Fields for Tab "BPO Alert Reporting"
The following selection criteria are available for BPMon alerts:
- Solution-Branch - Solution/Branch for which alerts should be evaluated
- System Role - System role relevant for the reporting (e.g. should the alerts for the QAS systems or the PRD systems be displayed)
- Context - Business Process context relevant for the evaluation
The following drill-down option is available for BPMon alerts:
- System - Flag this if you want to see the system information in the Key Figure Tables
Selection Fields for Tab "AO Alert Reporting"
The following selection criteria are available for AO alerts:
- Managed Object Type - To do the analysis for all alerts of a specific managed object type, e.g. database alerts
- Alert Category - To do the analysis for all alerts of a specific alert category, e.g. alerts related to performance
The following drill-down option is available for AO alerts:
- System - Flag this if you want to see the system information in the Key Figure Tables
- Alert Name - Flag this if you want to see the alert names in the Key Figure Tables
Key Figure Pie Charts
When the data is loaded, it might be that not all pie charts are displayed You can select/de-select pie charts via the following icon:
In case that the entered selection criteria are not too restrictive, for both data sources, BW and Alert Store, and in both tabs, AO and BPO, the following key figures are displayed as pie charts:
(Click picture to enlarge)
|Key Figure||Description||BW||Alert Store|
|Number of Alerts per Status||This key figure displayes the number and distribution of alerts that were created within the defined time span and that are currently in one of the following status:|
The key figure tells how high the workload for the OCC was in the specified time span and shows whether the OCC was able to handle the workload.
|Number of Alerts per Status|
When accessing the key figure "Number of Alerts per Status" from BW the status is derived from the assignment of an alert processor and confirmor.
|Number of Alerts per Processor||This key figure displays the number and the distribution of alerts that are currently assigned to a processor. The key figure considers alert of all status - not only status in process. It tells you how the workload within the OCC was distributed and whether there is improvement potential for the workload distribution. Per default, only anonymized information about the alert processors is displayed. If you want to see the clear names of the alert processor and this is legally allowed in your country, this is possible via additional authorization.||yes||yes|
|Number of Alerts with/without Incident|
This key figure displays the number and distribution of confirmed alerts, depending on whether an alerts has been confirmed with manual incident, with automatic incidents or without incident. This tells you whether you were able to prevent incidents via the OCC. Ideally, goal of the OCC should be to reduce incdent load, so alerts that are confirmed without incident give you an indication as to whether incidents were prevented. Additionally, this tells you how well the standard operating procedures for the OCC are documented. If you have many manually created incidents for alerts, this indicates that the standard operating procedures were not sufficent to solve the alert and may have to be improved.
Note: When accessing the data from the Alert Store the number of alerts with incidents is split up into manually and automatically created incidents.
|Number of Alerts per Confirmor||This key figure displays the number and distribution of alerts confirmed per user. This key figure tells you how the workload within the OCC was distributed. The technical users performing the auto-confirm are mentioned explicitly. Per default, only anonymized information about the alert confirmers is displayed. If you want to see the clear names of the alert confirmers and this is legally allowed in your country, this is possible via additional authorization.||yes||yes|
|Number of confirmed Alerts per Confirmation Classification||When an alert is confirmed the alert shall be classified. This classification information is evaluated here.||yes|
Number of confirmed Alerts per Confirmation Category
|When an alert is confirmed the alert shall be assigned to a confirmation category. In doing so it is possible to determine the number of false alerts. This category information is shown as a pie chart.||yes|
If there are no alerts or no confirmed alerts for the entered selection criteria found in the selected data source, you will see an information message, instead of the particular pie chart.
Filter Options for Key Figure Data in the Table Charts
For the key figures displayed as table charts you have additional filter and display options (Click picture to enlarge).
Filtering and Sorting Options for Table Charts
Filtering is based on the selected tab and the selected drill down options.
- Alert Name - If Drill Down to Alert Name is set (AO)
- Managed Object - String filter enables enhanced filtering functionality, e.g. all Managed Objects containing the string "ABAP"
- System - Allows to restrict the display to one specific system, if drill down to system is set (see the description of the selection fields in this article)
- Monitor (BPO) - Allows to restrict the display to specific monitoring functions (e.g. all ABAP Dump Monitors should be displayed)
Sorting can be done on every data column that is visible.
Display Features for Table Charts
In using the display features the table and the printout can be manipulated according to the needed data and screen format. You can fid the relevant relevant fields at the bottom of your screen
- Show Visible lines
- Allows you to determine how many lines should be contained in a table. If there are more entries than lines, the table will have several pages that you can go through
- Flag "Show Numbers"
- Columns for the Alert Numbers will be displayed in the key figure tables (click picture to enlarge).
- Flag "Monitor" (BPO)
- Column with the name of the monitoring function will be displayed in the key figure tables (click picture to enlarge).
With drag and drop it is always possible to changed the column sequence. In changing the column widht you might even minimize certain columns.
Key Figure Table Charts
The key figure tables look as follows (click picture to enlarge)
The following key figure can be displayed as table charts:
|Key Figure||Description||BW||Alert Store|
|Number of Alerts||This key figure table contains detailed information for the corresponding pie chart. It tells you whether the alerts were evenly distributed between the monitoring objects or whether there are some monitoring objects with a significantly higher number of alerts. This may indicate underlying problem and could trigger problem management procedures and improvement activities for these alerts. Improvement activities may include adjustements of the monitoring configuration.||yes||yes|
|Number of Alert Instances (Events)||This key figure should be evaluated in combination with the number of alerts. Both the number of alerts and the number of alert instances should below for each monitoring object. Therefore, a high number for individual monitoring objects should trigger improvement activities.||yes||yes|
|Maximum Duration until Alert Confirmation (in minutes)||Normally, alerts that occured should be solved in a timely manner. The duration until alert confirmation tells you how long it took to solve an alert, so this key figure tells you whether there are monitoring objects that had unusually long resolution times. This might indicate insufficient documentation of error hanlding procedure or more severe problems in the business process/application implementation and should trigger improvement activities to the monitoring concept or the business process / application implementation.||yes for the last 7 days|
|Maximum Duration until Manual Alert Confirmation (in minutes)||This is a refinement of the key figure "Maximum Duration until Alert Confirmation", which is available for BW. Different from the key figure "Maximum Duration until Alert Confirmation" the evaluation is done only on alerts which have been confirmed manually. It reveals the real maximum processing times, by excluding alerts, which have been automatically confirmed by the system after a defined time span has passed.||yes|
|Average Duration until Alert Confirmation (in minutes)||This key figure should always be considered in combination with the maximum duration until alert confirmation. It helps you identify whether most alerts for a monitoring object took long to resolve or just some.||yes|
|Average Duration until Manual Alert Confirmation (in minutes)||This is a refinement of the key figure "Average Duration until Alert Confirmation", which is available for BW. Different from the key figure "Average Duration until Alert Confirmation" the evaluation is done only on alerts which have been confirmed manually. It reveals the real average processing times, by excluding alerts, which have been automatically confirmed by the system after a defined time span has passed.||yes|
|Number of Confirmed Alerts with/without Incidents|
Normally, purpose of establishing an OCC is to achieve more stable operations. Ideally, this should result in fewer incidents created. All alerts are considered critical situations that would normally result in incidents. So to some extend, the number of alerts that were confirmed without incidents tells you the sucess of the OCC and the operations concept as they give you an indication about incidents that have been avoided by the monitoring concept.
Note: If the data are read from the Alert Store, the number of alerts with incidents is splitted up so that it is transparent, whether the alerts triggered the incident creation automatically or if the processor created the incident manually.
|Number of Alerts with Incidents||This key figure tells you for how many alerts an incident has been triggered, both manually and automatically.||yes|
|Number of Alerts with Manually Created Incidents||Ideally, the OCC should be able to solve the alerts without manually creating incidents. So every manually created incident indicates that the operating procedures defined were not sufficient for solving the alert situation, therefore this number gives you some kind of indication about the quality of the implemented standard operating procedures and can help identify improvement potential for your monitoring concept.||yes|
|Number of Alerts with Automatically Created Incidents||This key figure tells you per monitoring object how many automatic incidents were created per monitoring object. Automatic incidents usually mean that for whatever reason during the monitoring implementation is was decided that these alerts should not be handled by the OCC. As there are different reasons possible for this (too much expertise required, missing error handling documentation) this key figure gives you an indication about further improvement potential for the monitoring concept.||yes|
|Maximum Alert Response Times (in minutes)|
Regardless of how long it takes the OCC to solve alerts, the initial response to the alert should be rather quick. This key figure measures how long it took for each monitoring object until an alert processor was assigned. This tells you whether the initial response time to alerts was as expected.
Every key figure table displays the available data. In case there is no data (e.g. if no alert was confirmed, there is no max. duration until alert confirmation), an empty table is displayed. In case the data can be meaningfully separated for yellow and red alerts, the red bars display the value for the red alerts and the yellow bars display the values for the yellow alerts. Via mouse-over you can always see the actual values, even if you have choosen not to display them in the table (click picture to enlarge).
The monitoring objects in the tables are sorted by default descending, first by the first value, which is in most cases the number related to the red alerts, and afterwards by the second value, which is in most cases the number related to the yellow alerts. By clicking on the a table column the sorting can be adapted to the users needs.
Drill Down per Day/Month
All table charts offer forward navigation via the bars to the trend for the respective reporting key figure and monitoring object (double-click on the bar).
This is loading and displaying the data for the managed object alert name combination drilled down by day or month. The switch between daily or monthly aggregation is done according to the lifetime of the daily alerts in BW. This is set in SOLMAN_SETUP in the housekeeping settings of the technical monitoring. By default the lifetime is 90 days.
(Click picture to enlarge).
In this detailed screen you can change the type of diagram used. With a right-click in the diagram you can activate in the context menu the visibility of the data lables and legend or switch the whole diagram between a horizontal or vertical display, which is exchanging the axes.
Go back to the previous screen via the high-lighted back icon, not via the back function of your browser,
Via the respective icons you always have the option to print the tables, print the pie charts and export the tables to MS Excel. Printing via an PDF Exchange server allows the creation of PDF download for the tables and pies.
(Click picture to enlarge.)
To get a useful printout, you may prepare the table charts via the display features described above.
- No labels