Guided Procedure Activity Plugins

Focused Run for SAP Solution Manager provides activity plug-ins automating different tasks. The plug-ins help you to develop your own guided procedures that include tailored, automatic activities. These activities can be triggered manually or executed entirely in the background as part of an alert reaction, service level reporting, health check  guided or regular operational task procedure.

Proceed as follows to include a new plug-in activity in your guided  procedure:

  1. Select the relevant step.
  2. Select Automatic Activity > New.
  3. Choose Select a Plug-in and select the required plug-in from the value help.
  4. Rename the activity.
  5. Maintain the plug-in design-time attributes per your requirements.
  6. Select OK.
  7. While the new activity is selected, click Help text > New.
  8. Enter a name for the documentation.
  9. Enter a suitable documentation text. Click Save.
  10.  Use the Move up or Move down buttons to change the order of activities in the step.

SAP delivers many plug-ins that can be easily customized and included into your own guided procedures. The available plug-ins are explained below.

Purpose

You can use this guided procedure plug-in to assess the following key performance indicators (KPIs) for different tasks types:

  • Average response time

  • Database time

  • CPU time 

  • Number of steps per hour

Prerequisites

This plug-in is available only for ABAP systems.

Attributes

Define the following attributes for the plug-in:

  • Reporting Period: Specify the period for which you want to generate the report. You can enter the last n weeks or months.

  • Reporting Granularity: Specify the level of detail in which you want the results to be shown. You can choose between the total results, or the results broken down by month or day.

  • Task Type: Select the task type for which you want to view the performance metrics.

  • Metrics: Specify the KPI that you want to assess.

Data Source

The plug-in gets its data from reader CL_STATRAGG_READER.

Result

The result is displayed as a line chart showing the average response time, database time, and CPU time for each task over a given time frame. It also shows the number of steps based on the attributes that you selected.

Purpose

You can use this guided procedure plug-in to check aborted jobs in ABAP technical systems.

The plug-in retrieves all aborted jobs in the given time frame and groups them by job name.

Prerequisites

This plug-in is available only for ABAP systems.

Attributes

Define the following attributes for the plug-in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are: 

  • Read Time Frame from Alert: If the guided procedure is started from the Alert Inbox, select this option to read the time stamp from the alert.

  • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).

  • Specify Custom Time Frame: Select this option to read the time stamp defined in the Time Frame attribute.

  • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:

  • TODAY (current day from 00:00)

  • XXm (last XX minutes)

  • XXh (last XX hours)

  • XXd (last XX days, including a full day) 

  • YESTERDAY (previous full day)

  • CURRENT_WEEK (from Monday 00:00 to now)

  • LAST_WEEK (from Monday 00:00 to Sunday 23:59)

  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart.

Data Source

The aborted jobs are retrieved via RFC call from managed ABAP System.

Result

Both the table and the bar chart show the number of aborted runs for the top n aborted jobs or job types. 

Purpose:

This guided procedure plug-in shows the  installed languages in the managed ABAP  system.

Prerequisites:

  • This plugin- is available as of FRUN 2.0 FP01

Data Source:

- Installed languages data is retrieved using the CCDB store: SMLT_LANGUAGES.

Result:

  • Table Chart Output
  • Log Output:

The following log messages are returned by the plugin depending on the result of the check

  • <N> installed languages found. (Success)
  • No data found. (Error)

Purpose

This guided procedure plug-in is displays errors reported in the TMS Transport Logs of  the managed ABAP system.

Prerequisites

  • FRUN 2.0 FP01 or higher
  • ST-PI version 740 Support package 11 has to be installed on the managed ABAP System.

Data Source

- Data is retrieved using the ST-PI data provider: /SDF/CL_GPCR_CHECK_TRANS_ERROR

Result

  • Table Chart Output
  • Log Output

The following log messages are returned by the plugin depending on the result of the check

  • No Errors detected in TP System Log    (Success)
  • Errors detected in TP System Log (Error)

Purpose:

This guided procedure plug-in displays qRFC queues in waiting and error state.

Prerequisites:

  • FRUN 2.0 FP01 or higher
  • This plugin works only for ABAP systems.
  • ST-PI version 740   Support package 11 has to be installed on the managed ABAP System.

Design Time Attributes:

You can configure the following parameters:

  • Direction (Inbound or outbound queue)
  • Check queues in error state (A checkbox to filter on queues in qstate =ANORETRY, CPICERR, SYSFAIL, VBERROR)
  • Check queues in waiting state (A checkbox to filter on queues in qstate =WAITING, WAITSTOP, WAITUPDA)
  • Display top N queues
  • Sort by
  • Show only queues older than n days

Data Source:

- qRFC queues in waiting and error state is retrieved using the ST-PI data provider: /SDF/CL_GPCR_CHECK_QRFC_QUEUE

Result:

  • Table Chart Output
  • Log Output

The following log messages are returned by the plugin depending on the result of the check:

  • <N> qRFC Queues in waiting status detected. (Warning)
  • <N> qRFC Queues in error status detected. (Error)   
  • No queues in error or waiting state found. (Success)   
  • No SDA Agent running or no destination available for ABAP Technical System FT4. (Error)

Purpose:

This guided procedure plug-in is designed to trigger a specific task list in the managed ABAP system and monitor the task list run execution and its tasks status.

The task list run which will be created is related to the current GP instance. As long as the user is editing the same GP instance, the plug-in is monitoring the same task list run, so that any further execution of the plug-in on this GP instance will check the status of the related task list run.

However, a first execution of the plugin in a new GP instance will trigger a new task list run of the specified task list.

Prerequisites:

  • This plugin- is available as of FRUN 2.0 FP01
  • This plug-in works only for managed ABAP systems with releases 7.4 and higher.
  • ST-PI version 740 Support package 11 has to be installed on the managed ABAP System.
  • This plugin- triggers the execution of the specified task list via SDAGENT user in the managed ABAP System. The required authorizations are not included in the standard roles SAP_FRN_SDAGENT* of the SDAGENT user.
    To be able to execute the task list, SDAGENT user needs to have SAP BASIS Administrator roles in the relevant managed ABAP system.

Design Time Attributes:

You can configure the following parameters:

  • Task List Name: Name of the task list to check if it exists or trigger it if not    
  • Task List Variant: Variant of the task list to which it'll be assigned when triggered    
  • Wait for Result: A checkbox to either wait for the result or not if task list is still running    
  • Timeout (in minutes): Threshold of waiting time in minutes (if "Wait for Result")    
  • Show Successful Checks: A checkbox to either show successful checks or not    
  • Show Warning Checks: A checkbox to either show warning checks or not    
  • Show Error Checks: A checkbox to either show red checks or not    
  • Show Unprocessed Checks: A checkbox to either show unprocessed checks or not    
  • Show Task Logs: A checkbox to either show log messages of tasks not    
  • Check to be excluded <N>: Name of Task to be skipped in list execution    

Example of plug-in configuration:

We take as example of task list: SAP_BASIS_SYSTEM_CONFIG_CHECK

SDAGENT user needs to have SAP BASIS Administrator roles to be able to trigger the task list.

1- Adding the plug-in to the GP:

  • Open the GP in Edit Mode
  • Select your GP step -> Step Content -> Automatic Activities -> New -> Select a Plugin -> Plug-In
  • Select the plug-in ABAP Execute Task List

2- Filling plug-in attributes

  • Task List Name: SAP_BASIS_SYSTEM_CONFIG_CHECK
  • Task List Variant: Enter the name of a variant that exists in the managed system or leave it empty
  • Wait for Result: X
  • Timeout (in minutes): 2
  • Show Successful Checks: X
  • Show Warning Checks: X
  • Show Error Checks: X
  • Show Unprocessed Checks: X
  • Show Task Logs: X
  • Check to be excluded 1: CL_STCT_CHECK_RFC_DESTINATION
  • Check to be excluded 2: CL_STCT_CHECK_JOB_STATUS
  • Check to be excluded 3: CL_STCT_CHECK_USER
  • Check to be excluded 4: CL_STCT_CHECK_PROFILE_PARAMS

3- Trigger the task list:

After editing and saving the GP, execute a new instance of it in an ABAP managed system.

  • Execute the ABAP Execute Task List plug-in for the first time in the current GP instance.
  • The plug-in will prompt to trigger SAP_BASIS_SYSTEM_CONFIG_CHECK in the managed system and return logs and result data.
  • Any further execution of the ABAP Execute Task List plug-in on this current GP instance will only retrieve the result of the task list and won’t trigger it again, because the task list run is per GP instance. To trigger it again, a new GP instance (GP execution with new instance) is needed.

Data Source:

  • Task List related data is retrieved using the ST-PI data provider: /SDF/CL_GPCR_TASK_LIST_CHECK_N
  • Task List is triggered using the ST-PI data provider: /SDF/CL_GPCR_TASK_LIST_TRIGG_N

Result:

  • Table Chart Output showing the details of the task list checks.
  • Log Output:

The following log messages are returned by the plugin depending on the result of the check

  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> is still running after <N> minutes. Please try again later. (Warning)
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> failed (errors occurred). (Error)   
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> finished successfully. (Success)   
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> has been triggered successfully. (Success)   
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> finished with warnings. (Warning)    
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> is <Task List Status>. (Error)   

Possible errors:

Failed Task List Trigger

Log message:

  • Trigger of Task List <Task List Name> with variant <Variant ID> failed with error message: <error message>

Purpose:

This guided procedure plug-in checks whether  that all services preparation recommendations are implemented in the managed ABAP System . 

Prerequisites:

ST-PI version 740 Support package 11 has to be installed on the managed ABAP System.

Design Time Attributes:

No design time attributes required.

Data Source:

It performs an RFC call into the managed ABAP System and reads data from the Service Preparation Check (ABAP report RTCCTOOL )

Result:

  • Table Chart Output
  • Log Output:

The following log messages are returned by the plugin depending on the result of the check

  • All service preparation check recommendations are implemented. (Success)
  • Missing or incomplete service preparation check recommendations detected. (Error/warning)

Purpose

You can use this guided procedure plug-in to check the status of your system license.

The plug-in can also remind you that your license will be overdue in a specific number of days.

Prerequisites 

This plug-in is available only for ABAP systems.

Attributes

Define the following attributes for the plug-in:

  • Threshold for Red Rating: Enter the number of days until the license will become overdue to generate an error in the result. For example, a value of 5 will return an error for any licenses that expire within the next five days. 

  • Threshold for Yellow Rating: Enter the number of days until the license will become overdue to generate a warning in the result. For example, a value of 10 will return a warning for any licenses that expire within the next ten days.

Data Source

License data is retrieved via RFC Call from managed ABAP System

Result 

The result is displayed as a table containing the system ID, product ID, license key, expiry date, and the validity status.

Purpose

You can use this guided procedure plug-in to evaluate the buffers on each instance of the managed system.

Prerequisites

  • This plug-in is available only for ABAP systems.

  • The user SDAGENT_<SID> in the managed ABAP system  requires authorization object S_ADMIN_FCD with field STOR.

Attributes

Define the following attributes for the plug-in:

  • Minimum Threshold for Hit Ratio (%): Enter a number that represents the minimum threshold in percent for the hit ratio. If the hit ratio is below this threshold, the activity will be rated red.

  • Maximum Threshold for SWAPS: Enter a number that represents the maximum threshold in percent for the buffer swaps.If the buffer swaps exceed  this threshold, the activity will be rated red.

Data Source

Buffer data is retrieved via RFC Call from managed ABAP System

Result

The result is displayed as a table containing the instance name, buffer name, hit ratio, and swaps. A link is also provided so that you can check the result directly in transaction ST02.

Purpose

You can use this guided procedure plug-in to analyze the client change settings in an ABAP technical system. This check is only relevant for production systems.

Prerequisites

This plug-in is only relevant for ABAP production systems.

Attributes

Define the following attributes for the plug-in:

  • Optional Check: Specify whether you want to check CATT and eCATT authorization.

Data Source

The check is based on the CCDB Store CLIENTS:

  • Group name: SYSTEM-CHANGE-OPTION

  • Alias: SYSTEM-CHANGE-OPTION

  • Sub-alias: CLIENT-SETTING

Result

Log messages indicate whether client settings are correct or not for production systems.

Purpose

You can use this guided procedure plug-in to check dialog and HTTP response times from the system monitoring metric data for the selected ABAP technical systems.

You can define a threshold for each response time category.

Prerequisites

  • This plug-in is available only for ABAP technical systems.

  • The following monitoring metrics must be active for the current scope:

  • HTTP Response Time: ABAP_INST_ASR_HTTP_TOTAL

  • HTTPS Response Time: ABAP_INST_ASR_HTTPS_TOTAL 

  • DIALOG Response Time: ABAP_INST_ASR_DIA_TOTAL

Attributes

Define the following attributes for the plug-in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:

  • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).

  • Specify Custom Time Frame: Select this option to read the time stamp defined in the Last n Days attribute.

  • Last n Days: Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:

  • TODAY (current day from 00:00) 

  • XXm (last XX minutes)

  • XXh (last XX hours)

  • XXd (last XX days, including a full day)

  • YESTERDAY (previous full day)

  • CURRENT_WEEK (from Monday 00:00 to now)

  • LAST_WEEK (from Monday 00:00 to Sunday 23:59)

  • Granularity: Specify the level of detail in which you want the results to be shown.

  • Graphic Type: Specify whether you want the result to be displayed as a table, column chart, or line chart. 

Data Source

  • Data is retrieved from system monitoring.

  • The metrics HTTP Response Time, HTTPS Response Time, and DIALOG Response Time are considered.

Result

The result is displayed as a table, column chart, or line chart depending on the attributes that you configured for the plug-in.

Purpose

You can use this guided procedure plug-in to analyze IDocs with errors in your managed system. Different attributes are available to filter and classify the IDocs. A direct link is also provided so that you can access transaction DB87.

Prerequisites

This plug-in is only available for ABAP technical systems.

Attributes

Define the following attributes for the plug-in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:

  • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).

  • Specify Custom Time Frame: Select this option to read the time stamp defined in the Time Frame attribute.

  • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:

  • TODAY (current day from 00:00)

  • XXm (last XX minutes)

  • XXh (last XX hours)

  • XXd (last XX days, including a full day)

  • YESTERDAY (previous full day)

  • CURRENT_WEEK (from Monday 00:00 to now)

  • LAST_WEEK (from Monday 00:00 to Sunday 23:59)

  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart.

  • IDoc Direction:

  • Inbound

  • Outbound

  • Inbound and Outbound 

  • Threshold for Red IDoc Status: The system checks whether the number of IDocs categorized as "red" exceeds the value you enter here. If so, a log is written, and the activity is rated as red.

  • Threshold for Yellow IDoc Status: The system checks if the number of IDocs categorized as "yellow" exceeds the value you enter here. If so, a log is written, and the activity is rated as yellow.

  • Codes for Green IDoc Status: Specify the codes used to classify an IDoc with a green status. (Multiple codes should be separated by comma, for example, 51,52,53.)

  • Codes for Red IDoc Status: Specify the codes used to classify an IDoc with a red status (Multiple codes should be separated by comma, for example, 51,52,53.)

  • Codes for Yellow IDoc Status: Specify the codes used to classify an IDoc with a yellow status (Multiple codes should be separated by comma, for example, 51,52,53.)

  • Message Types: Specify the types of IDoc message to be considered. Multiple message types must be separated by a comma (,).

  • Clients: Specify the clients to be considered when reading the IDoc. Multiple clients must be separated by a comma (,).

Data Source

Data is retrieved via RFC call in managed ABAP system.

Result

The result is displayed as a table containing the client, message type, status code, number of updated IDocs, and the state.

Purpose 

You can use this guided procedure plug-in to analyze the availability of ABAP instances from the System Monitoring metric data.

The plug-in allows operators to check whether an ABAP instance is still unavailable before they start to investigate further within the guided procedure. The plug-in can also be added at the end of a guided procedure to check whether the actions performed to resolve the instance availability were successful.

Prerequisites 

  • This plug-in is available only for ABAP systems.

  • The following monitoring metrics must be active for the current scope:

  • ABAP_INSTANCE_STATUS

  • ABAP_INSTANCE_LOCAL_HTTP_AVAIL 

  • ABAP_LOCAL_RFC_AVAILABILITY

  • ABAP_LOCAL_LOGON_TEST

Attributes

Define the following attributes for the plug-in: 

  • Check "Local RFC Instance Availability"

  • Check "Local HTTP Instance Availability"

  • Check "Instance Status from SAPSTARTSRV"

  • Check "Local Instance LOGON TEST" 

Data Source

Data is retrieved from system monitoring. The names of the ABAP Instance Availability metrics are taken into consideration.

Result

The result is display as a table containing the system ID, instance name, metric name, status, message, and the time stamp at which the measurement took place. 

Purpose

You can use this guided procedure plug-in to analyze lock entries for ABAP managed systems.

The plug-in performs two types of check:

  • It checks users who have multiple lock entries. 

  • It checks entries that have been locked for over a certain number of hours.

Prerequisites

This plug-in is available only for ABAP systems.

Attributes 

  • Red Threshold for Old Entries (Hours): Specify the number of hours for which an entry can be locked before a red result is returned. The default value is 24 hours.

  • Red Threshold for Number of Entries per User: Specify the amount of entries that a user can lock before a red result is returned. The default value is 10,000 entries.

  • Check Mode: Select whether the plug-in is to check the old lock entries or the users who have multiple locks.

Data Source 

Lock entries are retrieved via RFC Call from managed ABAP System

Result

The result is displayed as a table containing the number of lock entries older than the specified number of hours, or the users with more lock entries than specified.

Purpose

You can use this guided procedure plug-in to determine whether the runtime of active jobs from the managed system exceeds a given threshold.

Prerequisites

This plug-in is available only for ABAP systems. 

Attributes

  • Red Threshold for Batch Job Runtime (Minutes): Specify the threshold for the runtime, as of which an error will be generated in the report.

  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart.

Data Source 

Related long-running jobs are retrieved via RFC Call from managed ABAP System

Result

The result is displayed as a table or bar chart containing the job name and runtime in minutes.

Purpose

You can use this guided procedure plug-in to perform two types of checks on ABAP managed technical systems: You can check for long-running work processes and you can check the work process statuses (in PRIV mode). 

Prerequisites

This plug-in is available only for ABAP systems. 

Attributes

Define the following attributes for the plug-in: 

  • Yellow Threshold for Dialog Tasks (Seconds): Specify the runtime in seconds after which a warning is to be issued for the dialog work processes.

  • Red Threshold for Dialog Tasks (Seconds): Specify the runtime in seconds after which an error is to be issued for the dialog work processes. 

  • Yellow Threshold for Batch Tasks (Seconds): Specify the runtime in seconds after which a warning is to be issued for the batch work processes.

  • Red Threshold for Batch Tasks (Seconds): Specify the runtime in seconds after which an error is to be issued for the batch work processes. 

  • Check Long-Running Work Processes: Select this checkbox to check long-running work processes.

  • Check Work Process Status: Select this checkbox to check work process statuses (in PRIV mode). 

Data Source

Related long-running work processes are retrieved using the SAPControl data provider. 

Result

The result is displayed as a table containing the task type, instance, work process number, status, time, program name, and rating. 

Purpose: This activity plugin checks memory on each instance of the managed system

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes: Red Threshold for used Memory (%) above

Data Source: Memory Statistics data is retrieved using RFC Data Provider

Output Result:

  • Charts: The table shows the Instance name, the Memory Area and the Used memory (%)
  • Logs:
    • Success (Green): All memory areas below threshold
    • Error (Red): Used Memory for <memory area> on instance <instance name> is above the Red Threshold.
    • Error (Red): Activity Memory Statistics can only be executed on ABAP Systems.

 

Purpose: This activity plugin checks number range objects which is greater than buffer filling degree defined by customer, and if the buffer filling percent is over threshold

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Buffer filling degree Threshold for Red Rating (%)
  • Buffer filling degree Threshold for Yellow Rating (%)
  • Show only number ranges above (%)

Data Source: Data is retrieving using RFC Data Provider.

Output Result:

  • Charts: Table shows Object name, Percentage of filling degree and status
  • Logs:
    • Success (Green): All number range objects have a filling degree below Yellow threshold
    • Warning (Yellow): <number of objects> number range objects where the filling level exceeds the Yellow Threshold.
    • Error (Red): <number of objects> number range objects where the filling level exceeds the Red Threshold.
    • Error (Red): Activity Memory Statistics can only be executed on ABAP systems.

Purpose: This activity plugin is used in a service level report and allows to report the Response Time Distribution KPI.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Reporting period Period for reporting data:
    • Last week
    • Last 2 weeks
    • Last 3 weeks
  • Reporting granularity Possible values:
    • Total
    • Month
    • Day
  • Display values as Possible values:
    • % of steps
    • Number of steps
  • Dialog Task type checkbox.
  • RFC Task type checkbox.
  • HTTP Task type checkbox.

Data Source:

Output Result:

  • Charts: Table shows the Period, Task Type, Steps and the duration per segments
  • Logs:
    • Success (Green): The table above shows the response time distribution of all Task types for the reporting period <reporting period> in percentage of executed steps.
    • Success (Green): The table above shows the response time distribution of all Task types for the reporting period <reporting period> in number of steps.
    • Success (Green): The table above shows the response time distribution of Task types <selected task types> for the reporting period <reporting period> in percentage of executed steps.
    • Success (Green): The table above shows the response time distribution of Task types <selected task types> for the reporting period <reporting period> in number of steps.
    • Warning (Yellow): No data were found for the reporting period <reporting period>
    • Error (Red): This activity can only be executed for ABAP Systems.
    • Error (Red): This system is not configured for ABAP performance KPI collection.

Purpose: This activity plugin perform check SAP Default Password on ABAP Technical System.

Prerequisites: This Plugin is only for ABAP systems.

Design Time Attributes: No Design time attribute can be defined for this health check.

Data Source: The Check is based on a CCDB Store.

Output Result:

  • Charts: Table with CLient, User, Password Status, Exists, Locked, Rating 
  • Logs:
    • Success (Green): Client change settings of productive client is not modifiable
    • Success (Green): This check is relevant for Production Client only. The current system doesn't have any productive client.
    • Error (Red): Client change settings of productive client 200 allow modifications.

Possible Errors: No CCDB store Exists

Purpose: This activity plugin performs a check on ABAP Short Dumps

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Timeframe Source: start timestamp and end timestamp
    • Read Timeframe from Alert
    • Read Timeframe from GP Attributes
    • Specify custom Timeframe
  • Timeframe: Value used only if Timeframe Source is set ti Read Timeframe from GP Attributes
  • Write timestamp as log message: Check flag to specify if the timestamp should be written in the guided procedure log
  • Select the graphic type: Select Table or Bar Chart style
  • Enter the number of rows to display: Maximum number of top logs to display in the output
  • Old Data provider: Flag of using old Data Provider

Data Source: There is an old RFC data provider and a new one. The way data are retrieved can be controlled at design time using a specific attribute.

Output Result:

  • Charts: The table shows the Component name, the Runtime Errors, the Program name and the occurrence of the dumps. !the bar chart show the Top <N> shortdumps per number of Occurrence . 
  • Logs: 
    • Information:<N> Shortdumps occurred in the timeframe <Start time> to <End time>
    • Error (Red): Activity Short Dumps can only be executed on ABAP Systems.

Purpose: This activity plugin checks if SNC is active

Prerequisites: This plugin works only for ABAP systems

Design Time Attributes: No design time attributes can be defined for this health check

Data Source: SNC Status is retrieved using RFC Data Provider

Output Result:

  • Charts: Table shows the System ID, the Instance Name, the SNC status and the timestamp.
  • Logs:
    • Success (Green): SNC is active on instances <instances name>
    • Error (Red): SNC is not active on instance <instance name>
    • Error (Red): Get SNC Status data failed

Purpose: This activity plugin performs a check on transmission requests numbers group by different status on managed system. It checks also if the number of transmission requests with different status is more than threshold defined by the user.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Timeframe Source: Source for reading the evaluation timeframe: Start timestamp and End timestamp. Possible Values are:
    • Read Timeframe from GP Attributes
    • Specify custom Timeframe
  • Timeframe: Time range for searching transmission requests information , the input value should be an integer value and must end with time unit "d" or "h" or "m"
  • Number of messages with status Error: Threshold for number of transmission requests with status Error.
  • Number of messages with status Waiting: Threshold for number of transmission request with status Waiting

Data Source: Transmission Request data is retrieved using RFC data provider

Output Result:

  • Charts: The Table  shows the CLient number, The Error Messages and number, the Number of transmission requests and the Status
  • Logs:
  • Success (green): Less than <N> Waiting transmission requests found in the timeframe from <Start timestamp> to <End timestamp>.
  • Error (Red): More than <N> Error transmission requests found in the timeframe from <Start timestamp> to <End timestamp>
  • Error (Red): Activity SOST Transmission request can only be executed on ABAP systems

Purpose: This activity plugin help to identify errors or delays in spool processing.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Timeframe Source: Source for reading the evaluation timeframe: Start timestamp and End timestamp. Possible Values are:
  • Timeframe: Value used only if Timeframe Source is set to Read Timeframe from GP attributes
  • Select the graphic type: Table or Bar Chart
  • Threshold for Red rating if number of Waiting spool requests exceeds
  • Threshold for Red rating if number of Failing spool requests exceeds
  • Threshold for Red rating if number of Spool requests without output request exceeds
  • Use old data provider Flag

Data Source: There is an old RFC data provider and a new one. The way data are retrieved can be controlled at design time using a specific attribute.

Output Result:

  • Charts: The table shows the CLient, the Error Message and Number, the Number of Transmission requests and the Status. The Bar CHart shows the Number of Successful and cancelled Spool requests per type of Spool requests
  • Logs:
    • Info (Blue): Spool requests created in the following timeframe were evaluated from <start timestamp> to <end timestamp>
    • Success (Green): No Update errors were detected in the timeframe from <start timestamp> to <end timestamp>
    • Success (Green): Number of successful spool requests: xx
    • Success (Green): <N> spool requests without output requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Success (Green): <N> failed spool requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Success (Green): <N> Waiting spool requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Error (Red): More than <N> spool requests without output requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Error (Red): More than <N> failed spool requests detected in the timeframe from <start timestamp> to <end timestamp> 
    • Error (Red): More than <N> Waiting spool requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Error (Red): Activity Spool requests cqn only be executed on ABAP Systems.

Purpose: This activity plugin verify that all standard reorg jobs have been executed successfully.

Prerequisites: This plugin works only for ABAP Systems

Design Time Attributes: No design time attributes can be defined for this health check.

Data Source: Jobs related data is retrieved using RFC data provider.

Output Result:

  • Charts: Table shows the Job names, Program name, Interval, Last Job Execution, Last Job Status, Results of execution and status
  • Logs: 
    • Success (Green): All standard reorg Jobs have been executed successfully at the expected time
    • Error (Red): Problems with standard reorg Jobs were detected
    • Error (Red): No data retrieved. Call to data provider <data provider> failed with Error <error message>
    • Error (Red): Activity Standard Job can only be executed on ABAP Systems

Purpose: This activity plugin checks ABAP System Availability based on System Monitoring  data. It provides a quick overview whether system is available or not at the time of the health check execution

Prerequisites: This plugin work only for ABAP systems.

  • ABAP_SYSTEM_RFC_AVAILABILITY
  • ABAP_SYS_RFC_LOGONGROUP_SPACE
  • ABAP_MESSAGE_SERVER_HTTP_AVAIL

Design Time Attributes:

  • Check System Availability via "RFC Ping"
  • Check System Availability via "ABAP Message Server HTTP Availability"
  • Check ABAP RFC Availability (Logon Group SPACE)

Data Source: Data is retrieved from system monitoring. The ABAP system availability metrics “Check System Availability" via "RFC Ping", "Check System Availability" via "ABAP Message Server HTTP Availability", ABAP RFC Availability (Logon Group SPACE are taken into account).

Output Result:

  • Charts: Table shows Metric name, Status of system availability, Message from the metric, Measured Timestamp
  • Logs:
    • Success (Green): System is available (RFC/HTTP)
    • Success (Green): System is not available via HTTP due to planned downtime (WM = 010)
    • Error (Red): System <SID> is not configured for monitoring
    • Error (Red): System is not available (RFC / ABAP message server HTTP / Logon Groupe SPACE)
    • Error (Red): Data Collection timestamp older than 5 minutes
    • Error (Red): Could not retrieve metric details ABAP_SYSTEM_RFC_AVAILABILITY (From UDM Store)

Possible Errors:

  • Could not retrieve metric details for <metric type>: Metrics are not active for scope
  • No Check selected: No metrics were selected from the design time
  • Activity System Availability can only be executed on ABAP systems: Selected scope is not ABAP system

Purpose: This activity plugin perform check on System Change Settings on ABAP Technical System. This check is only relevant for Production System.

Prerequisites: This plugin is only for ABAP production systems.

Design Time Attributes: None

Data Source: The check is based on a CCDB Store GLOBAL:

  • Group name: SYSTEM-CHANGE-OPTION
  • Alias: SYSTEM-CHANGE-OPTION
  • Sub-alias: GLOBAL-SETTING

Output Result:

  • Charts: None
  • Logs:
    • Success (Green): System change settings of productive system is not modifiable.
    • Success (Green): This check is relevant for Production Systems only. The current system is set to QA System.
    • Error: System change setting of productive system is modifiable !

Possible Errors: The IT Admin Role must be Production System

Purpose: This activity plugin performs check on ABAP System logs

Prerequisites: This plugin works only for ABAP Systems

Design Time Attributes:

  • Timeframe Source: Source for reading the evaluation timeframe: start timestamp and end timestamp. Possible values are:
    • Read Timeframe from Alert
    • Read Timeframe from GP Attributes
    • Specify custom Timeframe
  • Timeframe: Value used only if timeframe source is set to read timeframe from GP Attributes
  • Select the Graphic type: Table or Bar Chart
  • Enter the number of rows to display: Maximum number of top system logs to display in the output. Let it empty if you want them all
  • Use old data provider flag
  • New data provider without text replacement (faster): Select it to use text replacement without text replacement which is faster but log info less detailed.
  • Write timestamp as log message: Select it to display in log section: "The following timeframe was evaluated from <timestamp> to <timestamp> timezone CET"

Data Source: There is an old RFC data provider and a new one. The way data are retrieved can be controlled at design time using a specific attribute.

Output Result:

  • Charts: The table shows the Full message ID, the Type of the System Log Error, the Last Occurrence and the number of Errors. The Bar chart shows the Number of Errors per System Logs
  • Logs:
    • Info (Blue): <N> system log messages were logged in the timeframe from <start timestamp> to <end timestamp>
    • Error (Red): Activity System Logs can only be executed on ABAP Systems.

Purpose: This activity plugin check if Update Process is up and running and if number of update error and update in initial state from the managed system are not exceeding a given threshold.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Timeframe Source: Source for reading the evaluation timeframe: start timestamp and end timestamp - possible values are:
    • Read Timeframe from GP Attributes
    • Specify custom timeframe
  • Last n Days: Read Data from the last n Days (Default is 1 - for all update errors you can specify a value of 0).
  • Select the graphic type: Graphic type display in output report: Bar Chart or Table
  • Check status of update service: Check if the update service process is up and running
  • Report update errors: Check if the number of update errors is exceeding the given threshold
  • Show Name of ABAP report: Display graphic report update errors
  • Enter the threshold for red rating for updates in error state: Threshold for the number of update errors
  • Report updates in initial state: Check if the number of update in initial state is exceeding the given threshold

Data Source: Data is retrieved using RFC data provider

Output Result: Logs

  • Success (Green): No Update request(s) in errors were detected in the time frame from <start time> to <end time>
  • Success (Green): <N> Update request(s) in errors were detected in the time frame from <start time> to <end time>
  • Success (Green): No Update request(s) in initial state were detected in the time frame from <start time> to <end time>
  • Success (Green): <N> Update request(s) in initial state were detected in the time frame from <start time> to <end time>
  • Success (Green): Update service is active: Update Service is up and running
  • Warning (Yellow): No check selected: At least one check should be selected at design time
  • Error (Red): <N> Update request(s) in errors were detected in the time frame from
  • Error (Red): <N> Update request(s) in initial state were detected in the time frame from
  • Error (Red): Update service is inactive: Update Service is not running
  • Error (Red): No data retrieved. Call to data provider /SDF/CL_GPCR_GET_UPDATE_STATUS failed with error: <error message>
  • Error (Red): Activity Update Status can only be executed on ABAP systems.

Purpose: This activity plugin checks the current Work Processes configuration on ABAP Managed System.

Prerequisites: This Plugin works only for ABAP Systems

Design Time Attributes: Select the graphic type Table or Bar chart.

Data Source: Data is retrieved using SAPCONTROL Data Provider

Output Result: 

  • Charts: The table shows the Instance name, Workprocess Type and Number of Configured Workprocesses. The Bar chart shows the Configured WorkProcesses per Instance name and workprocess type.
  • Logs: 
    • Success (Green): Current Work process configuration is displayed
    • Error (Red): No destination available for ABAP Instance <instance name>
    • Error (Red): Activity Work Process Configuration can only be executed on ABAP systems.
    • Error (Red): No instance defined for this technical system

Purpose: This activity plugin displays the availability status of services for a BOBJ system.

Prerequisites: This plugin works only for BOBJ systems.

Design Time Attributes:

Technical Metric Name: Name of Technical Metric (Default is BOE SERVER STATE CMS)

Data Source: Data is retrieved from system monitoring.

Output Result:

  • Charts: Table shows the server name, the Availability, the Timestamp and the Rating
  • Logs:
    • Success (Green): All BIP Server are Available
    • Error (Red): No BIP Server State Monitoring metrics were found for instance <instance name>
    • Error (Red): Some BIP Server State monitoring metrics could not be collected for instance <instance name>
    • Error (Red): Availability problems detected for instance <instance name>
    • Error (Red): Activity BOBJ Server State can only be executed on BOBJ Systems
    • Warning (Yellow): No BOBJ Central Management Server Instance found for <SID>

Purpose: This activity shall be used in all alert handling guided procedures to display other open alerts for the system, database, instances of the system and hosts.

Prerequisites: Configure the alert and attach it to the GP.

Design Time Attributes: No design time attribute can be defined for this health check

Data Source: Data is retrieved from Alert Management

Output Result:

  • Charts: Table shows the Alert Name, the Category, the Managed Object
  • Logs:
    • Success (Green): No other alerts are open
    • Error (Red): Other open alerts were found

Purpose: This activity shall be used in all alert handling guided procedures to displays current status of related alert and metrics.

Prerequisites: Configure the alert and attach it to the GP.

Design Time Attributes: No design time parameter required

Data Source: Data is retrieved from Alert Management

Output Result:

  • Charts: Table shows the Metric Name, The First, Worst, Last, Min, Max, Last Value and Text.
  • Logs:
  • Success (Green): The current rating of the alert is Green
  • Error (Red): The current rating of the alert is Red

Purpose: This activity plugin may be used to check configuration & security analytics of a specific policy based on CCDB stores.

The main used case for this plugin is to allow an operator to check analysis of the related policy for the selected system.

Prerequisites: This plugin needs a valid CSA policy for the selected scope.

Design Time Attributes:

  • CSA Policy: CSA Policy Name
  • Display only Non-Compliant Items: Display only checks were compliance rating is red
  • Relevant for: Execute for the Technical System or related System Database
  • Ignore Policy validity check: Disable the checking for CSA Policy namz validity
  • Show details: Generate the data table with the results

Data Source: Policy related data is retrieved using CCDB data provider

Output Result:

  • Charts: the table shows the Compliant Status, Ladscape, Description, Configuration item, Value, Check, Rule and Timestamp.
  • Logs:
    • Success (Green): All Checks are compliant
    • Warning (Yellow): There is no valid check item for the executed context. Check, if the policy is valid for the managed Object.
    • Error (Red): Number of non-compliant checks: <N>
    • Error (Red): Could not execute CSA Policy.

Purpose: This activity plugin may be used to check Total and Used Data Volume for a database from the System Monitoring metric data.

The main use case for this plugin is to allow an operator to check that the used data volume of the database in question is less than the specified threshold.

Prerequisites: This plugin works only for HANA, Maxdb, DB2, Sybase ASE and Oracle databases.

Design Time Attributes:

  • Timeframe Source:
    • Specify custom Timeframe
    • Read Timeframe from GP Attributes
  • Timeframe Selection: Last <N> days
  • Threshold for Red rating: Used Volume (%). Default is 77%.
  • Display Data as Line or Bar Chart.

Data Source: Data is retrieved from system monitoring. Metrics names are taken into consideration.

Output Result:

  • Charts: Line Chart shows the Database Size in GB over the Total Data Volume and Used Data Volume. Bar Chart shows the Database size (%): Total Data Volume and Used Data Volume over the timeframe.
  • Logs
    • Success (Green): No Problem with Database size detected for Database <DB Name>.
    • Error (Red): Problem with Database size detected for Database <DB Name>.
    • Error (Red): No Database size found for Database <DB Name> in timeframe <start timeframe> to <end timeframe>.
    • Error (Red): This activity works only for HANA, Maxdb, DB2, Sybase ASE, Oracle and not for <Database Type>.

Purpose: The activity mainly used for executing custom operations deployed in the host agents of the managed system from the guided procedure custom operation on managed system's hosts.

 

Prerequisites: Operation which has been deployed on agent are only considered.

Design Time Attributes:

  • Operation Name: Custom operation name to be executed
  • Arguments: Operation's arguments format is as argmentName1=argumentValue1; argumentName2=argumentValue2
  • Execution Scope: Execution Scope of operation. Ex: All hosts, central host, DB hosts.
  • Time Out: Timeout parameter of this operation which determine operation method synchronous(EQ -1) or asynchronous (GE 0)
  • Wait for result: Determine by user whether he needs to wait the result to be retrieved or only trigger.
  • Helper Class: used for helping user to set input, evaluate output, set execution scope. The class should inherit from the interface IF_CUST_OPERATION_HELPER and implement the helper class by user himself.

Data Source: Data is retrieved via host agent data provider:

  • EXE_CUST_OPERATION: Used for execute custom operation.
  • IS_OPERATION_FINISHED: For judging if operation has finished.
  • GET_OPERATION_RESULT: For getting operation result with operation-ID.

Output Result:

  • Charts: Tables shows Hostname, Operation, Operation Result
  • Logs:
    • Success (Green): Operation has been executed successfully on all scope
    • Error: Operation SAPHostAgent.Ping did not finish on host <hostname> after 30 seconds.

Possible Errors: Operation dbconnect is not defined in sub-directory operations.d of SAPHostAgent on <hostname>

Purpose: This Health Checks may be used to check the status of a database via saphostcontrol operations “GetDatabaseStatus, GetDatabaseSystemStatus, GetDatabaseProperties.

Prerequisites: This plugin is for Technical Systems, Database and Hosts.

Design Time Attributes: Function name: Possible saphostcontrol functions: GetDatabaseStatus, GetDatabaseSystemStatus, GetDatabaseProperties, ListDatabaseMetrics, ListDatabaseConfiguration.

Data Source: Data is retrieved via Host Agent Data provider

Output Result:

  • Charts: Table shows Hostname, Key, Value, Returned Status
  • Logs:
    • Success (Green): All DB components are running
    • Success (Green): Execution of saphostcontrol <function> was successful on <host(s)>. Please review the results.
    • Error (Red): Some DB components have errors.
    • Error (Red): Status of some DB components could not be retrieved.

Possible Errors:

No Database host were found for Database <DBID>. Please check Database definition in LMDB.

Purpose: This Health Checks allows to check the status of an ABAP or SAP J2EE System  database via sapcontrol operations: ABAPGetWPTable, ABAPGetSysWPTable,  GetProcessList, J2EEGetProcessList, J2EEGetProcessList2

Prerequisites: This plugin is for Technical Systems, Database and Hosts.

Design Time Attributes. The Activity plugin is configured via design time attributes selection: Operation - Possible sapcontrol commands: ABAPGetWPTable, ABAPGetSysWPTable, GetProcessList, J2EEGetProcessList, J2EEGetProcessList2

Data Source: Data is retrieved via saphostcontrol

Output Result:

  • Table Chart: Instance name, Name, PID, Description, Dispstatus, Text Status, Start Time, Elapsed Time
  • Bar Chart: None
  • Logs:
    • Success: Operation <xxx> has been executed successfully
    • Error: Operation <xxx> has Failed on some hosts. Communication Error with SDA. No SDA running or no destination available for ABAP Instance

Purpose: This activity plugin perform check on ABAP or JAVA the Expiring Server Certificates.

Prerequisites:

  • This plugin is only for ABAP and JAVA systems.
  • The relevant CCDB data collector should be configured and running.

Design Time Attributes:

  • Enter the threshold for red rating: Number of days before the server certificate expires (error message). 7 days by default.
  • Enter the threshold for yellow rating: Number of days before the server certificate expires (warning message). 60 days by default.

Data Source: The check is performed on CCDB stores located on the Solution Manager.

Output Result:

  • Charts: Table shows Instance Name, Available certificate, Serial number, Expiry date, Status of the certificate
  • Logs:
    • Error (Red): No Certificate data found for <instance> in Change  reporting in the PSE_CERT store (CCDB store not found).
    • Error (Red): <xxx> number of certificates have expired.
    • Error (Red): Permission denied: Content Authorization missing (CCDB stores reading permissions).
    • Error (Red): Store not existing (CCDB store not found).
    • Error (Red): Error - Unexpected exception
    • Error (Red) Number of certificates will expire in less then <xxx> Days.
    • Success: All certificates are valid for more then <xxx> Days.

Possible Errors:

No Certificate data found for instance

Purpose: This activity plugin may be used to check the backup of the Hana database from the System Monitoring metric data.

Prerequisites:

  • This plugin works only for HANA Database
  • The monitoring metrics cited below should be active for the current scope:
    • HDB_BACKUP_AGE_METR_37
    • HDB_EXISTENCE_OF_DATA_BACKUP_34
    • STATUS_OF_MOST_RECENT_DATA_BACKUP_36_HDB

Design Time Attributes: No design time parameter required.

Data Source: Data is retrieved from System Monitoring. The Data Backup metrics name are taken into consideration.

Output Result:

  • Charts: None
  • Logs: 
    • Success (Green): Current Data backup is available
    • Warning (Yellow): DBMS type of <SID> is not an HANA DB, operation aborted
    • Warning (Yellow): No Primary Database defined
    • Error (Red): No Data Backup exists
    • Error (Red): Status of most recent Data Backup is not OK
    • Error (Red): Most Recent Data Backup is older than 1 day
    • Error (Red): No current metrics for Data backup found

Purpose: This activity plugin may be used to check whether the space usage of the HANA database is < than 90%.

The main used case for this plugin is to allow an operator to check that the used space of Hana database System is high or not.

Prerequisites:

  • This plugin works only for HANA DB.
  • The monitoring metrics cited below should be active for the current scope:
    • HDB_HOST_CPU_IDLE_005
    • HOST_CPU_IDLE

Design Time Attributes:

  • Threshold for red rating (%)
  • Timeframe

Data Source: Data is retrieved from system monitoring. The CPU usage metrics name are taken into consideration

Output Result:

  • Charts: Graphic shows the HANA Overall CPU Usage over a given timeframe
  • Logs:
  • Success (Green): No problems with HDB Host CPU usage detected
  • Warning (Yellow): DBMS type of <SID> is not HANA Operation Aborted
  • Error (Red): HDB Host CPU usage is high
  • Error (Red): No Current monitoring metrics for HDB Host Memory usage found.

Purpose: This activity plugin may be used to check HANA long running threads from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the long-running Blocking Situations, Tasks, Statements, Uncommitted Write Transactions or Serializable Transactions is lower than the threshold.

Prerequisites:

  • This plugin works only for HANA DB.
  • The monitoring metrics cited below should be active for the current scope:
    • HDB_STATISTICS_METRIC_049
    • HDB_STATISTICS_ALERT_096
    • HDB_STATISTICS_METRIC_039
    • HDB_STATISTICS_METRIC_047

Design Time Attributes:

  • Check Long Running Blocking Situation
  • Check Long Running Tasks
  • Check Long Running Statements
  • Check Long Running Serializable Transactions

Data Source: Data is retrieved from system monitoring. The Long running metrics name are taken into consideration

Output Result:

  • Charts: The Graphic shows the Long Running Threads (Serializable and Blocking) for a given time range
  • Logs:
    • Success (Green): No <metric-name> were detected
    • Success (Green): No Long running <metric-name> were detected on database
    • Warning (Yellow): DBMS type of <SID> is not HANA, Operation Aborted
    • Error (Red): <metric-name> running for more then <threshold> minutes were detected on database
    • Error (Red): No current monitoring metrics for <metric-name> found on database

Possible Errors: No current metrics for Long Running Thread found

Purpose: This activity plugin may be used to check the HA/DR of the Hana database from the System Monitoring metric data.

Prerequisites:

  • This plugin works only for HANA DB
  • The monitoring metric cited below should be active for the current scope:
    • HDB_AVL_1015_REPLICATION_STATUS

Design Time Attributes: No design time parameter required

Data Source: Data is retrieved from system monitoring. The replication metric name are taken into consideration.

Output Result:

  • Charts: None
  • Logs:
    • Success (Green): System replication is active.
    • Success (Green): System replication is not configured for this database. No system replication check required
    • Warning (Yellow): DBMS type of SQU is not HANA, Operation Aborted
    • Warning (Yellow): No Primary database defined
    • Error (Red): Problems with system replication detected
    • Error (Red): No SR Replication status metrics found for virtual DB <Virtual DB Name> and on Physical primary <Virtual DB Name>
    • Error (Red): No Primary physical database found for virtual DB <Virtual DB Name>

Purpose: This activity plugin may be used to check space usage of the Hana database from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the space usage of the HANA database is < than 90%.

Prerequisites:

  • This plugin works only for HANA DB.
  • The monitoring metrics cited below should be active for the current scope:
    • HDB_EXP_002_DISK_USAGE_ALRT

Design Time Attributes:

  • Threshold for Red rating: Disk usage (%)
  • Timeframe
  • Last N days: Number of days
  • Granularity: 15m/Hour/Day

Data Source: Data is retrieved from system monitoring. The HANA DB Space metrics name are taken into consideration.

Output Result:

  • Charts: Graphic shows the HANA DB disk usage data and log size for a given timeframe
  • Logs:
    • Success (Green): No problem with database disk usage detected.
    • Warning (Yellow): DBMS type of <SID> is not HANA, Operation Aborted
    • Warning (Yellow): No primary database defined
    • Error (Red): Database Disk usage is high
    • Error (Red): No current monitoring metrics for HDB Disk usage found.

Possible Errors: Metrics are not active for scope. No current monitoring metrics for HDB Disk usage found for database <DBSID>

Purpose: This activity plugin may be used to check HANA Used Memory from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the used memory of the HANA database is < than 90%

Prerequisites:

  • This plugin works only for HANA DB.
  • The monitoring metric cited below should be active for the current scope:
    • HDB_HOST_PHYS_MEM_METR_1

Design Time Attributes:

  • Threshold for Red rating: HANA Host Used Memory (%)
  • Timeframe
  • Last N Days: Number of Days
  • Granularity: Minutes/Hour/Day

Data Source: Data is retrieved from system monitoring. The HANA used memory metric name are taken into consideration.

Output Result:

  • Charts: Graphic shows the HANA Database Host Physical Memory Usage (%) over a given time frame.
  • Logs:
    • Success (Green): No Problem with HANA DB Host Memory usage detected.
    • Warning (Yellow): DBMS type of <SID> is not HANA, operation aborted.
    • Error (Red): HANA DB Host Memory usage is high.

Purpose: This activity plugin may be used to check the overall CPU utilization on all hosts of the managed systems from the System Monitoring metric data.

This activity shall be used for the health check gps to check that the overall CPU utilization on all hosts of the managed systems for the last days is below 70%. 

Prerequisites: The monitoring metric cited below should be active for the current scope: CPU_UTILIZATION_5MIN

Design Time Attributes:

  • Threshold for red rating: HANA Host CPU usage (%)
  • Timeframe

Data Source: Data is retrieved from system monitoring. The CPU usage metrics name are taken into consideration.

Output Result:

  • Charts: Graphic shows the CPU Utilisation (%) over the given timeframe.
  • Logs:
    • Success (Green): Average CPU utilization was always below <red Threshold> % detected
    • Error (Red): CPU utilization <red threshold> % detected
    • Error (Red): No current metrics for Host CPU utilization found

Purpose: This Health Checks may be used to check disk usage on the hosts of the managed systems, databases.

Data can be displayed in graphic and log message.

Prerequisites: None

Design Time Attributes:

  • Disk usage threshold: threshold on space usage of each file system. Used tu judge if the free space of special file system is enough.
  • Max Retries: Defined how many times we need to try, when error occurred such as connection to system failed.

Data Source: 

Output Result:

  • Charts: Table shows The hostname, Mount path, File system path, Size (GB), Free (GB), Used (GB), file system usage (%), Status.
  • Logs:
    • Success (Green): No File Systems with more than xx% usage detected
    • Error (Red): x File Systems with more than xx% usage detected.
    • Error (Red): Cannot connect to Agent after sometimes tries.

Possible Errors: 

  • No hosts retrieved from the scope <SID> on <Hostname>. 
  • Error Message: Cannot connect to Agent after xx times tries.

Purpose: This Health Checks may be used to check the top CPU processes running on the hosts of the managed systems. Get and analysis usage percent of top CPU process, then display them within graphic and log message.

Prerequisites: This plugin is for Technical Systems, Database and Hosts.

Design Time Attributes:

  • Threshold of CPU usage: Need a % value. Ex: 90 - Threshold of CPU usage is 90%
  • Max Number of tries: How many times we need to try if error occurred such as connecting to hosts failed.
  • Number of top CPU process: Need a Number. Ex: 10 - Top ten CPU processes

Data Source: The CPU process data is retrieved via Host Agent Data provider

Output Result:

  • Charts: Barchart Shows Host / Process with CPU usage (%)
  • Logs:
    • Success (Green): No OS Processes with more then 10% CPU consumption detected
    • Error (Red): Cannot Get Data from Agent - Error occurred when calling LR8GPD8HOST -> GET_DATA() usually because of bad RFC connection to Host.
    • Error (Red): 15 OS Processes with more than 0.1% CPU consumption detected over all Hosts.

Possible Errors: Cannot Get Data from Agent

Purpose: This activity plugin may be used to check JAVA Instance Availability from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the JAVA Instance is still not available before performing any further investigation within the guided procedure. This activity plugin can also be added at the end of the guided procedure to check if the action performed to solve the JAVA Instance Availability was successful.

Prerequisites:

  • This plugin works only for JAVA systems.
  • The monitoring metrics cited below should be active for the current scope:
    • 'JAVA_SCS_ENQUEUE_STATUS'
    • 'JAVA_SCS_MESSAGE_SERVER_STATUS'
    • 'PORTAL_INST_STARTPAGE_AVAILABILITY'
    • 'JAVA_INSTANCE_HTTP_AVAILABILIT'
    • 'JAVA_ICM_STATUS'

Design Time Attributes: No Design time attribute can be defined for this health check

Data Source: Data is retrieved from system monitoring. The JAVA Instance Availability metrics name are taken into consideration.

Output Result:

  • Charts: Table shows the Instance name, System ID, Metric Name, Value, Status
  • Logs:
    • Success (Green): All JAVA Instances are available
    • Warning (Yellow): JAVA Instance Availability can only be executed on JAVA systems
    • Error (Red): Problems with JAVA Instance availability detected
    • Error (Red): System is not configured for monitoring

Purpose: This activity plugin may be used to check JAVA System Availability from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the JAVA System is still not available before performing any further investigation within the guided procedure. This activity plugin can also be added at the end of the guided procedure to check if the action performed to solve the JAVA System Availability was successful.

Prerequisites:

  • This plugin works only for JAVA systems.
  • The monitoring metric cited below should be active for the current scope: 'JAVA_SYSTEM_HTTP_AVAILABILITY'

Design Time Attributes: No Design time attribute can be defined for this health check

Data Source: Data is retrieved from system monitoring. The JAVA System availability metrics name are taken into consideration.

Output Result:

  • Charts: Table shows the System ID, Metric Name, Status, Message, Timestamp collection
  • Logs:
    • Success (Green): HTTP ping to destination was successful, system is available
    • Success (Green): System <SID> is not available via HTTP due to planned downtime
    • Error (Red): System Monitoring Metric JAVA_INSTANCE_HTTP_AVAILABILITY is not configured
    • Error (Red): System <SID> not configured for monitoring.
    • Error (Red): System is not available via HTTP. HTTP ping failed.
    • Error (Red): Data collection time stamp older then 5 minutes
    • Error (Red): Could not retrieve metric details JAVA_INSTANCE_HTTP_AVAILABILITY

Purpose: This activity plugin is used in a service level report and allows to report the Outages related KPI.

Prerequisites: Scope objects must have a service definition in SAM.

Design Time Attributes:

  • Number of Reporting Periods: Number of former reporting periods (either months or weeks). Default 3.
  • Include current Reporting Period: Either include current reporting period or not.
  • SLA Relevant: Outage type as checkbox.
  • Not-SLA Relevant: Outage type as checkbox.
  • Confirmed: Outage type as checkbox.

Data Source:

Output Result:

  • Charts: Table shows The Outage Start, end, Duration and Reason.
  • Logs:
    • Success (Green): No outages were detected for the reporting periods from <start period> to <end period>.
    • Success (Green): No SLA relevant outages were detected for the reporting periods from <start period> to <end period>.
    • Warning (Yellow): Unconfirmed outages were detected for the reporting periods from <start period> to <end period>.
    • Error (Red): No service definition exists for <Scope ID>

Purpose: This activity plugin shall be used in a service level report and shall provide an overview over upcoming planned downtimes.

Prerequisites: None

Design Time Attributes: Show data for next N weeks, default is 12.

Data Source:

Output Result:

  • Charts: Table show the Planned Downtime start, End, Duration (min), Category and Reason
  • Logs:
    • Success (Green): The table above lists the upcoming planned downtimes until <end date>
    • Success (Green): No upcoming planned downtimes until <end date> found

Purpose

You can use this plug in to retrieve and scan log errors that are generated by the SAP ASE database in file /$SYBASE/$SYBASE_ASE/install/server_name.log. The plug in enables you to customize the location of the log file.

Prerequisites

This plug in works for systems with SAP Adaptive Server Enterprise database

Design Time Attributes

Define the following attributes for the plug in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:
  • Read Time Frame from Alert: If the guided procedure is started from the Alert Inbox, select this option to read the time stamp from the alert.
  • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).
  • Specify Custom Time Frame: Select this option to read the time stamp defined in the Time Frame attribute.
  • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:

-              TODAY (current day from 00:00)

-              XXm (last XX minutes)

-              XXh (last XX hours)

-              XXd (last XX days, including a full day)

-              YESTERDAY (previous full day)

-              CURRENT_WEEK (from Monday 00:00 to now)

-              LAST_WEEK (from Monday 00:00 to Sunday 23:59)

  •  Write Time Stamp as Log Message: Select this check box to include the time stamp in the guided procedure log.
  • Root Directory of Log File: Enter the root directory for the log file for example: /sybase
  • Path to Log File: Enter the relative path to the log file. Wildcard characters are supported, for example: ${SID}/ASE-*/install/${SID}.log
  • Report User Errors: Select this checkbox to include user errors in the report (with a severity between 10 and 16).
  • Report Internal Errors: Select this checkbox to include insufficient resources and internal errors in the report (with a severity between 17 and 18).
  • Report Fatal Errors: Select this checkbox to include fatal errors in the report (with a severity between 19 and 26).

Data Source

The plug performs a call to the SDA of the database host  to scan the log file(s)

Result

The result is displayed as a table containing the severity, error number, state, and message.

Purpose: To check whether the ASE Job Scheduler is running from the System Monitoring metric data.

Prerequisites: 

  • This plugin works only for ASE SYBASE DB.
  • The monitoring metric indicated below should be active for the current scope: ASE_DBCTRL_JS_STATUS

Design Time Attributes: No Design time attribute can be defined for this health check.

Data Source: Data is retrieved from system monitoring. The Job Scheduler metrics name are taken into consideration.

Output Result:

  • Charts: None
  • Logs: 
    • Success (Green): SAP ASE DB Job Scheduler Status: <Metric Text>.
    • Warning (Yellow): DBMS type of <SID> is is not ASE DB, Operation Aborted.
    • Error (Red): SAP ASE DB Job Scheduler Status: <Metric State>.
    • Error (Red): No Current monitoring Metrics for SAP ASE DB Job Scheduler Status found.

Possible Errors: SAP ASE DB Job Scheduler Status : <x>, Job Scheduler is not running

Purpose: To check long running processes of the SAP ASE Database 

 

Prerequisites:

This plugin works only for Sybase database.

The monitoring metrics cited below should be active for the current scope:

  • ASE_LONGEST_TX_SID
  • ASE_LONGEST_TX_OTHERS
  • ASE_LONGEST_TX_saptools
  • ASE_LONGEST_TX_MASTER
  • ASE_LONGEST_TX_MODEL
  • ASE_LONGEST_TX_sybmgmtdb
  • ASE_LONGEST_TX_SYBSECURITY
  • ASE_LONGEST_TX_sysbystemdb
  • ASE_LONGEST_TX_sybsystemprocs

Design Time Attributes:

  • Threshold for red rating: if runtime exceeds (seconds)
  • Timeframe
  • Last N Days: Number of days
  • Granularity: Hour / Day / Minutes
  • Select the graphic type: Bar chart / Table

Data Source: Data is retrieved from system monitoring. 

Output Result:

  • Charts: Bar chart or Table shows the Database name and Maximum Runtime
  • Logs:
    • Success (Green): No long running transactions were detected in the timeframe from <Start> to <End>
    • Warning (Yellow): DBMS type of <SID> is not ASE, Operation Aborted
    • Error (Red): Transactions running for more than <Red Threshold>, seconds were detected on databases <database names list, e.g. saptools, master, ...> in the Timeframe from <start> to <end>
    • Error (Red): No current monitoring metrics for ASE Long Running Transactions found.

Possible Errors:

Purpose: This activity plugin may be used to check the space usage of the sybase database from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the space usage of the Sybase database is < than 90%.

Prerequisites:

  • This plugin works only for Sybase database.
  • The Data & Log metrics cited below should be active for the current scope:
  • Data:
    • ASE_FREE_SPACE_PCT_SID
    • ASE_DB_FREE_RATIO_saptools
    • ASE_DB_FREE_RATIO_SYBSECURITY
    • ASE_DB_FREE_RATIO_MASTER
    • ASE_DB_FREE_RATIO_model
    • ASE_DB_FREE_RATIO_SYBSYSTEMPROCS
    • ASE_DB_FREE_RATIO_sybmgmtdb
    • ASE_DB_FREE_SPACE_RATIO_SybSystemDB
    • ASE_DB_FREE_RATIO_OTHERS
  • Log:
    • ASE_FREE_LOG_PCT_SID
    • ASE_FREE_LOG_PCT_GRP_OTHERS
    • ASE_FREE_LOG_PCT_MASTER
    • ASE_FREE_LOG_PCT_MODEL
    • ASE_LOG_FREE_PCT_SYBMGMTDB
    • ASE_FREE_LOG_PCT_SYBSECURITY
    • SYB_LOG_FREE_PCT_SYBSYSTEMDB
    • ASE_LOG_FREE_PCT_SYBSYSTEMPROCS
    • ASE_FREE_LOG_RATIO_SAPTOOLS

Design Time Attributes:

  • Threshold for red rating: Disk usage (%)
  • Timeframe
  • Last N Days: Number of days
  • Granularity: Hours/Days/Minutes
  • Data or Log Space Metrics

Data Source: Data is retrieved from system monitoring. The Log / Data metrics name are taken into consideration.

Output Result:

  • Charts: Graphics shows the Used Data Space (%) over the selected Timeframe
  • Logs:
    • Success: Free Data / Log space for all Databases is bellow <x> %
    • Warning (Yellow): DBMS type of <SID> is not ASE DB, Operation aborted
    • Error (Red): Free Data / Log space for at least one database is above <x> %
    • Error (Red): No Current monitoring metrics for ASE Free Data Space / ASE Log Space found.

Possible Errors: Used Database for at least one Database is above 0 %.

Purpose: This Health Check may be used to check all OS processes started by SAPControl framework for a given technical system.

Prerequisites: This plugin is only for ABAP and HANA technical systems.

Design Time Attributes: No design time parameter required..

Data Source: Data is retrieved using the SAP Control source.

Output Result:

  • Charts: Table with Instance Name, Status, PID, Process Name, Description, Elapsed time, Start time, Status
  • Logs:
    • Error (Red): No destination available for ABAP Instance <InstName>

Purpose: This activity shall be used in all alert handling guided procedures to display the status of Simple Diagnostics Agents belonging to system or database. This is a prerequisite for most of the following troubleshooting activities.

Prerequisites: This plugin is for Technical Systems, Database and Hosts.

Design Time Attributes: No design time parameters required

Data Source: Data is retrieved from the Simple Diagnostics Agent.

Output Result:

  • Table Chart: Hostname (Status), Host Agent Name (Availability)
  • Bar Chart: None
  • Logs:
    • Success: All SDA are available - All SDA running on database or system instances are available.
    • Error: Problems with SDA detected - SDA are not available.

Purpose: This Health Checks may be used to check the user status in Managed System for all clients.

Prerequisites: This plugin is for Technical Systems, Database and Hosts.

Design Time Attributes:

  • Set Red rating if user or password expires in less than <N> days
  • Set Yellow rating if user or password expires in less than <N> days
  • List of Users (Separated by ";")

Data Source: Data is retrieved using RFC data provider

Output Result:

  • Charts: The table shows the Client, User, User Type, User End Validity, Password End Validity, Locked and Validity Status
  • Logs
    • Info (Blue): Password Validity check has not been performed as passwords will never expire (login / password_expiration_time=0)
    • Success (Green): No problem detected regarding user or password validity for the checked users.
    • Warning (Yellow): Problems detected regarding user validity for the checked users. user validity will expire for at least one checked user in less than <N> days.
    • Warning (Yellow): Problems detected regarding user or password validity for the checked users. Password will expire for at least one checked user in less than <N> days.
    • Error (Red): Problems detected regarding user validity for the checked users. User validity will expire for at least one checked user in less than 20 days.
    • Error (Red): Problems detected regarding user or password validity for the checked users. Password will expire for at least one checked user in les than <N> days.
    • Error (Red): No users provided to be checked
    • Error (Red): No metrics were selected from the design time