Skip to end of metadata
Go to start of metadata

Tab Overview 

Business Process Monitoring Wiki                                                         

Business Process Monitoring Setup in 7.2

Introduction

As of Solution Manager 7.2 SP07[1] in the area of Business Process Monitoring (BPMon) a lot of new key figures have been made available for the Dashboard Builder.

  • Key Figures evaluating the Alert Store Log
  • Key Figures showing up metrics values stored in the Short Term Cube

Additionally for all key figures evaluating the Alert Store and Alert Store Log a larger range of dimensions is offered.

This means the data of the assigned data sources can be drilled down to or can focus the analysis on certain aspects of the available alerts. If for example the analysis shall cover alerts with a guided procedure assigned only, this can be done by setting up a filter for the corresponding dimension.

New Dimensions

The following list shows which of the available dimensions are new for the Alert Store and the Alert Store Log Key Figures: 

Dimension NameTypical ExamplesUse CaseSP07+
Alert CategoryAvailablility, Configuration, Exception, PerformanceAlerts 
Confirmation ClassificationFalse Alert, SLA relevant, Non SLA relevantSLA relevant AlertsYes
Close ActionGreen alert, red alert, yellow alert, other reasonAlerts that have been closed by rating change / alerts that have been changed from red to yellow ratingYes
Confirm ActionAutomatically, Manually, IncidentAlerts confirmed manuallyYes
Confirmed by/OpenAutoconfirm user, anonymized user namesAccording to GDPR the authorization to see the real user names can be assigned 
Confirmation CategoryHardware - General, Hardware - Application Server, Software - DatabaseConfirmed Alerts that had to do with database issues 
Context TypeBPMon Object, Technical System, Job, Interface ChannelJobMon Alerts 
Datedepends on the housekeeping settings of the data source the key figure is related withHorizon of Alert Creation 
Timenumber of minutes into the pastAlerts of the last xx minutesYes
Has guided procedureYes, noAlerts with guided procedure assignedYes
Incident ID<incident ID>Alert which created incident with this numberYes
Incident TypeWithout incident, with automatically created incident, with manually created incidentAlerts with manually created incidentsYes
MonitorIDoc, Batch Jobs, ABAP Short DumpsAlerts for table entry counter alertsYes
Monitoring Object ID<monitoring object>Alerts for a specified monitoring object 
Monitoring Use CaseBPMon, Technical System Monitoring, Job MonitoringAlerts for job monitoring 
ProcessorAnonymized user namesAccording to GDPR the authorization to see the real user names can be assigned 
RatingRed, yellowRed alerts 
System ID<sid>Alerts for a system 
Solution Documentation ContextSelect from the solution documentation tree structureAlerts for a specific Business Process Step 
Alert StatusOpen, in process, transferred, confirmedOpen alerts 

 

New Key Figures

Alert Store Log Key Figures

With the following Key Figures the available timestamps of the different activities logged for the alerts can be calculated with one another or with the alert creation and end timestamps[2]. 

The timestamps of alerts that are immediately closed (e.g. Alerts showing up an event, such as a job that was canceled and not a permanent situation, such as the extremely high data volume in a table) are not considered for the alert age calculation.

 

Key FigureTechnical NameExplanation 

90% of Alerts assigned in .. minutes

MX_CRE_ASS_TCreation to Assignment Time 

Alerts assigned in average after .. minutes

AV_CRE_ASS_TCreation to Assignment Time 

90% of Alerts with Notification after .. minutes

MX_CRE_NOT_TCreation to Manual Notification Creation Time 

Alerts with Notification in average after .. minutes

AV_CRE_NOT_TCreation to Manual Notification Creation Time 

90% of Alerts with Incident after .. minutes

MX_CRE_INC_TCreation to Manual Incident Creation Time 

Alerts with Incident in average after .. minutes

AV_CRE_INC_TCreation to Manual Incident Creation Time 

90% of Alerts confirmed after .. minutes

MX_CRE_CON_TCreation to Confirmation Time 

Alerts confirmed in average after .. minutes

AV_CRE_CON_TCreation to Confirmation Time 

90% of Alerts with Notification .. minutes after Assignment

MX_ASS_NOT_TAssignment to Manual Notification Creation Time 

Alerts with Notification in average .. minutes after Assignment

AV_ASS_NOT_TAssignment to Manual Notification Creation Time 

90% of Alerts with Incident .. minutes after Assignment

MX_ASS_INC_TAssignment to Manual Incident Creation Time 

Alerts with Incident in average .. minutes after Assignment

AV_ASS_INC_TAssignment to Manual Incident Creation Time 

90% of Alerts confirmed .. minutes after Assignment

MX_ASS_CON_TAssignment to Confirmation Time 

Alerts confirmed in average .. minutes after Assignment

AV_ASS_CON_TAssignment to Confirmation Time 
90% of Alerts max. .. minutes aliveMX_ALG_AGE

Alerts: Creation to Technical End Time

If the alert is not closed, yet, the current moment (now) is taken for the calculation.

 

Alerts in average .. minutes alive

AV_ALG_AGEAlerts: Creation to Technical End Time

If the alert is not closed, yet, the current moment (now) is taken for the calculation.

 

90% of Incidents from Alerts are max. .. minutes alive

MX_INC_AGE

Incidents: Creation to Confirmation Time

If the incident is not confirmed, yet, the current moment (now) is taken for the calculation.

 

Incidents from Alerts are in average .. minutes alive

AV_INC_AGE

Incidents: Creation to Confirmation Time

If the incident is not confirmed, yet, the current moment (now) is taken for the calculation.

 

90% of Alerts were responded in .. minutes

MX_IRT_TInitial Response Time 
Alerts were responded in average in .. minutesAV_IRT_TInitial Response Time as of SP09

90% of Alerts were processed internally .. minutes

MX_IPT_TInternal Processing Time 
Alerts were processed internally in average in .. minutes AV_IPT_TInternal Processing Time as of SP09

90% of Alerts were processed externally  .. minutes

MX_EPT_TExternal Processing Time 
Alerts were processed externally in average in .. minutes AV_EPT_TExternal Processing Time

 as of

SP09

Find more information regarding the calculation of the IRT, IPT and EPT in the graphic  Maximum Alert Response Times.

Maximum Key Figures are cut by default at a maximum of 90% to exclude outliers. This percentage can be manipulated per user[3], although the Key Figure description text in the data source selection is fixed. Therefore make sure that you give each dashboard tile an appropriate and understandable heading, especially if one dashboard shall be used by different users.

Short Term Cube Key Figures

Besides the Metric Store and the (Long Term) BW Infocube, the newest metrics of the day can now also be accessed with its more detailed information that are typically lost after aggregation, from the short term BW Infocube.

These Key Figures are categorized in Dashboard Builder with the prefix STC (Example: STC/APPMON/KPPURCH303).

 

 

[1] On request a downport to SP05 or SP06 is possible via SAP Note.

[2] The end timestamp is either the technical close of an alert, due to rating change or alert confirmation or the current moment for unclosed alerts.

[3] Use report AGS_BPM_ALREP_RESET_DEFAULTS and delete for your user the persistency setting name DEFAULT_MAXCUT and overwrite it with the new persisted value as shown in the screenshot.

Hit F8. Then the new setting is saved. To verify, display the setting, that is persisted now for this user.

 

  • No labels