Workload Monitoring: Manually adding a TCODE for monitoring

Due to performance overhead and limited use we transitioned workload monitoring from wholesale to custom configurations. Here are the instructions how to add a single TCODE monitoring

1. Collection

Workload Statistics are not collected for all TCODEs anymore, in order to collect specific TCODE stats you need to explicitly configure a retriever (or create a dedicated retriever)

Navigate to the system of interest in the grid, click Retriever tool/leaf

An inactive retriever “Stats Summary Retriever” is always created, for easy of maintenance create a copy for each of type as needed:

• For TCODEs selection

• For TaskType (and TCODEs) selection

• For User (and TCODEs) selection

• Any combination of custom selector

Please be advised that Gateway/SAP overhead of a single retriever is repeated for each additional one: Stats Summary retriever always pulls/summarizes all STAT records for the interval, the On-Gateway retriever will enumerate all records returned from SAP and will match it to the selector, only matching records will be posted to IT-Conductor. Busy SAP system have thousands of STATS records per interval (normally 15 min) and this will create a significant overhead, so try to consolidate these retrievers as much as possible.

Retriever selectors

Open

Add/Modify the Insertion Criteria records, the drop-downs will suggest the values

Open

Normally you focus on:

• SAPDialogStep.TASKTYPE

• SAPDialogStep.TCODE

• SAPDialogStep.TERMINALID

• SAPDialogStep.ACCOUNT

All Insertion criteria works on “AND” basis

Use Exclusion criteria if needed, which will be applied after the Insertion Criteria so you can filter out undesired records

Modify the Read Interval if needed (default 15 min). This interval is for calculating the summary records and calculating the repeat executions of the retriever. If you set the interval to say 30 minutes, then 30 min average records for each TCODE/TASKTYPE/ACCOUNT/TERMINAL/TimeStamp combination will be created - you will not be able to zoom in time-wise below that. If you change it afterwards you will need to also update the associated aggregators or the end-data will not be accurate.

2. Aggregation

2.1 Consolidators

After the STAT Record objects (class SAPServiceAggregatorSTATSummaryTCODE) are created in IT-Conductor you need to configure the aggregation/threshold to make sense of the interval data. The individual TCODE Aggregators (SAPServiceAggregatorSTATSummaryTCODE) are automatically created (currently the template is disabled for overhead reason) however you will need to configure manually the so called Buckets (aka consolidators) that consolidate individual aggregator data into bucket data.

You can either create a new consolidator manually or add additional “source” to an existing consolidator. The “source” is a setup that define the criteria for inclusion of aggregators into the bucket. If you only need to monitor a single “standalone” TCODE you don't need a consolidator

The Threshold (monitor) is auto-created for Consolidator. But for individual (standalone) TCODE aggregator you will need to create one manually.

2.1.1 Threshold Override for Consolidators

Create a threshold override for Target Class=ConsolidatorSAPStats. (see sample below)

2.2 ThresholdCollector

An alternative, more modern and efficient way to aggregate the data is to use ThresholdCollector (SAPStatSummaryThresholdCollection). ThresholdCollector combines data record aggregation and value monitoring in one.

Modify an existing one to include more TCODE’s or create new one (https://service.itconductor.com/objectCreate?OBJECT_ClassName=SAPStatSummaryThresholdCollection)

Specify the Name
Select Value Attribute form the drop-down (default - SAPDialogStep.RESPTI)
Select Select Application (SAP NW) (optional)
Type in SAP Account (optional)
Type in TCODE Regex (any valid regex expression, case sensitive, use (?i) to turn off case sensitivity)
Type in Task Type list (comma-separated, optional, use TaskType Field Definition for numeric tasktype values)

Upon creation of the ThresholdCollector a new Workload container will be create (if doesn’t already exist) and will be discovered under the SAP Grid, the threshold will appear under it there as well

2.2.1 Threshold Override for ThresholdCollector

Create a threshold override for Target Class=SAPStatSummaryTCODE. (see sample below)