Technical Prerequisites

To be able to monitor SAP SLT replications you need:

  • SAP Focused Run 2.0 FP01

Please ensure that you have the software component DMIS either in version 2010* SP6 or higher or in version 2011* SP1 or higher available in the managed (monitored) SLT system. In addition, the SLT monitoring requires the following components to be in place in the SLT system:

  • ST-PI 2008_1 700 SP6 or higher
  • ST-A/PI 01P or higher

Integration Monitoring Setup

Available Monitoring Categories

The available monitoring categories are:

  • SLT: SLT replications between two systems (Monitoring transaction LTRO)

 

 

Available Filter Options

SLT

For SAP SLT monitoring you can monitor all SLT replications or use the following filter parameters to restrict the data collection:

  • Source System: Source system of the replication (Field Source System in transaction LTRS)
  • Target System: Target system of the replication (Field Target System in transaction LTRS)
  • SLT Schema: SLT configuration name (Field Configuration Name in transaction LTRS)
  • Status Group: Status group of the replication, choose ERROR or SUCCESS 
 

Available Metrics

For SLT replications the following metrics are collected:

SLT

  • Number of SLT replication with error: Number of SLT replications with errors
  • Status of metric "Load Jobs Config Not Run" is error: Number of configured but not running load jobs
  • Status of metric "Load Jobs Status" is error: Status of Data Load Job(s)
  • Status of metric "Load Jobs Terminated" is error: Number of terminated load jobs runs since the last refresh
  • Status of metric "Master Jobs Status" is error: Status of SLT Master Job
  • Status of metric "Source Status" is error: Monitors the connection status to Source System
  • Status of metric "Target Status" is error: Monitors the connection status to Target System
  • Status of metric "Trigger Active Status" is error: Checks whether the triggers are active for all tables of a configuration.
  • Status of metric "Trigger Status" is error: Checks whether a triggers is in error status
  • Violation of limit of metric "Avg Latency 1h":  This metric shows the median time taken for data replication over the last hour.
  • Violation of limit of metric "Avg Latency 24h": This metric shows the median time taken for data replication over the last 24 hours.
  • Violation of limit of metric "Load Jobs Nb Config": Number of configured load jobs
  • Violation of limit of metric "Master Jobs Terminated": Number of terminated master jobs runs since the last refresh
  • Violation of limit of metric "Max Entr To Repl For Sngl Tbl": Maximal number of table entries that are still to be replicated of a single table
  • Violation of limit of metric "Max Latency 1h": This metric shows the maximal time taken for a data replication over the last hour.
  • Violation of limit of metric "Max Latency 24h": This metric shows the maximal time taken for a data replication over the last 24 hours.
  • Violation of limit of metric "Nb Tables Not Fully Repl": Number of tables that are not fully replicated
  • Violation of limit of metric "Oldest Age Table Rep": Age of the oldest time stamp of a table entry that should be replicated
  • Violation of limit of metric "Schema Latency": This metric shows the median time taken for data replication over the last 24 hours per schema
  • Violation of limit of metric "Sum Table Entries to Repl": Sum of all table entries that are still to be replicated (for all tables)
  • Violation of limit of metric "Table Nb Error": Number of Tables in Error State
  • Violation of limit of metric "Table Nb To Repl": Number of tables to be replicated
  • Violation of limit of metric "Youngest Timestamp": Timestamp of the most recent replication of the a data record.