Business Process Monitoring

A germainAPM Business Process (BP) can be configured to follow processes through any number of sequential or repeating steps.  A BP can equate to a "scenario" that user(s) perform on a web application OR a BP can also be the correlation of data from any other data source and across data sources. 

Business Processes can be

  • Data driven
  • Click driven
  • Transaction driven

Business Process Definition

Each business process definition is defined under Analytics> Business Processes:


Attributes:

  • Name - Identifies this business process (should be unique among all BP definitions)
  • KeyExpression - Property to use to connect a single instance of this BP (usually a sessionId)
  • Latency - Expected latency of fact data (in seconds; default 120)
  • Timeout - ongoing BP will timeout after this time; BP status will be marked as "TIMED_OUT" (in seconds; default 300)
  • RecordTimeout - If true, will record BP in case of time-out otherwise we won't keep it
  • RecordTimeoutThreshold - Minimum progress (in %) required to record BP in case of timeout
  • RecordReset - If true, will record BP in case of reset otherwise we won't keep it
  • RecordResetThreshold - Minimum progress (in %) required to record BP in case of reset
  • bpClass - Model class used to store BPs generated from this definition (currently supported GenericBusinessProcess or SiebelBusinessProcess)
  • bpStepClass - Model class used to store BP steps generated from this definition (currently supported GenericBusinessProcessStep or SiebelBusinessProcessStep)
  • RecordOutsideSteps - If true, will record steps found outside of list of defined steps
  • OutsideFilters - Map of filter criteria for outside steps
  • Kpis - This BP will process any data generated for any of these KPIs
  • Steps - List of BP steps

Business Process Step Definition


A BP STEP is like a Business Milestone. For each business process step we define the following attributes (details below screenshot):

  • name - Business Process Step Name. Must be unique name for this BP defnition
  • recurring - If true, marks this step as ocurring one or more times
  • optional - If true, marks this step as optional
  • labelGenerator - MVEL expression to generate BP step label (e.g. "Click on " + siebel.view)
  • metrics - Metric definitions for this step (additional/optional metrics that we want to collect for a particular step - e.g. volume of user clicks between 2 steps)
  • filters - Map of filter criteria for this step


Filter criteria can be set for a BP/Step

Key of a specific filter is an attribute model (details on available model attributes are available here - Analysis Model Reference) and value corresponds to the data value. In the example above this particular BP Step is looking for a data point where name == GotoView and type == HTTP:Request and Siebel View == FINS Home Page.

Business Process KPI Definition


The KPI for a Business Process is configured very much the same as any other KPI. The important points are that the factCategory and factClass must match Business Process configuration, KPI's factClass must be equal to BP's bpClass and KPI's factCategory must be equal to BP's name. Example:

Business Process Portlet Configuration

If you want to see a Business Process flow, click on your dashboard "+ Add Metric" then switch to "Add a more complex metric" and select "BP Flow" as a portlet type:


Example

Examples using our old config console (all the concepts still apply, the UI to configure it is now different)

BP Definition

https://drive.google.com/open?id=1fc07hLmOeylj9HHiDmpojwarWFf5aya3

BP Steps Definition

https://drive.google.com/open?id=1Zy4WvYuysRXM0mrAh9vJha9QPOBnOlDk

BP KPI Definition

https://drive.google.com/open?id=1y8LEZZKkWO5XlAfS9ys0L-lG6eyxKMWi

BP Portlet Configuration

https://drive.google.com/open?id=1bTPDBUIzTXWDi7mzL1t5PKp7ZPLmm_2R