Guided Procedure Activity Plugins

With Focused Run FP3 SAP delivers predefined Alert Handling, Automatic Activity or Health Check plugins activities that can be used into customer Guided Procedures. It is also possible to develop customer specific automated activities. Automatic Activities can be triggered by a user or executed fully automatic in background within a Guided Procedure.

  • The Alert Handling plugins allows to define and automate alert reactions. They usually consist in problem context collection and resolution. It can be triggered automatically as soon as the alert was raised
  • The Automatic activity plugins execute certain predefined tasks automatically in background. Once executed they return a log message indicating success or failure of the activity and optionally a table, or other graphics with more details.
  • The system Health Check plugins performs several health checks on ABAP systems and sends out a result report with all findings to interested parties. It can be executed manually or scheduled to be executed automatically in regular intervals.

Purpose: This activity plugin shall be used in a service level report and shall allow to report the following KPis:

Average of the response time, Database time, CPU time and number of steps per hour for different task types during the reporting period.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Reporting period: Last N week
  • Reporting granularity: Total / Month / Day
  • Task Type: Dialog / HTTP / HTTPS / RFC
  • Metrics:
    • Average Response Time
    • Average Database Time
    • Average CPU Time
    • Number of Steps

Data Source:

Output Result:

  • Charts: Line Chart shows the Average CPU Time per task on the given timeframe
  • Logs:
    • Success (Green): The line chart above shows the average <Selected Metric> for Task type <task type> in the reporting preriod from <start date> to <end date>
    • Success (Green): The <selcted metric> for Task type <task type> was <value> <counter> in the reporting period from <start date> to <end date>
    • Warning (Yellow): No data where found for the reporting period from <start date> to <end date>
    • Error (Red): This activity can only be executed for ABAP System
    • Error (Red): This system is not configured for ABAP performance KPI collection.

Purpose: This activity plugin checks Aborted Jobs on ABAP Technical System.

It retrieves all aborted jobs for the given timeframe and group them per job name.

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 to Read Timeframe from GP Attributes.
  • Graphic type: select the desired Graphic Type (Table pr Bar Chart)
  • Use extended filters: Check if Extended Filters are used for this activity

Data Source: Related aborted jobs are retrieved using the RFC Data Provider.

Output Result:

  • Charts: The Table shows the Job Name and the number of aborted Jobs. The Graphic shows the Top 10 Aborted jobs.
  • Logs
  • Success (Green): No Job canceled between <Start Time> and <End Time>.
  • Error (Red): <number> jobs canceled between <Start Time> and <End Time>.
  • Error (Red): Activity Aborted Jobs can only be executed on ABAP systems.

Purpose: This activity plugin checks system license's status.

It also reminds if the status will be overdue in a number of days you specify.

Prerequisites: This plugin works only for ABAP systems

Design Time Attributes:

  • Threshold for Red rating: remaining days from today to the date when license overdue.
  • Threshold for Yelow rating: remaining days from today to the date when license overdue.

Data Source: License data is retrieved using the RFC Data Provider.

Output Result:

  • Charts: The table shows the System ID, the Product ID, the Licence Key, the Expiry Date and the Validity Status
  • Logs:
  • Success (Green): All licenses are Valid
  • Success (Green): No license found
  • Warning (Yellow): License <license key> will expire on <expiry date>. The number of days from now to expiration date is less than the yellow threshold.
  • Error (Red): License <license key> will expire on <expiry date>. The number of days from now to expirationdate is less than the red threshold.
  • Error (Red): License <license key> has expired.
  • Error (Red): Activity Active License can only be executed on ABAP systems.

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

Prerequisites:

  • This plugin works only for ABAP systems.
  • Needed authorization object: S_ADMIN_FCD with field STOR

Design Time Attributes:

  • Red threshold for Hit Ration % below
  • Red threshold for SWAPS exceeding

Data Source: Buffer's data is retrieved using the RFC Data Provider.

Output Result:

  • Charts: Thes Table shows the Instance name, the Buffer name, the Hit ratio and Swaps.
  • Logs:
    • Success (Green): no problem with buffer detected, each buffer's Hit Ratio is not below a given value and Swap is not exceeding a given value.
    • Error (Red): Buffers with low Hitratio or Buffer sawps detected. At least one buffer whose hit ratio is below the given <Red Threshold for Hit Ratio % below> or whose swaps is exceeding the given <Red Threshold for Swaps exceeding> detected.
    • Error (Red): No data retrieved. Call to data provider /SDF/E2E_BUFFER_INFO failed with error: <error_message>
    • Error (Red): Activity Buffers Statistics can only be executed on ABAP systems.

Purpose: This activity plugin perform check on Client 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: The Activity plugin is configured via design time attributes selection:

Optional Check: CATT and eCATT Authorization, CATT and eCATT Not Allowed.

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

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

Output Result:

  • Charts: None
  • Logs: 
    • Error (Red): Client change settings of productive client 200 allows modifications
    • 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

Possible Errors:

  • There are no clients on the CCDB Store
  • There are no productive client role

Purpose: This activity plugin may be used to check Dialog and HTTP Response Time from the System Monitoring metric data for the selected ABAP technical system:

Data are displayed within a graphic. Threshold can be defined for each Response Time Category

Prerequisites: This plugin is only for ABAP Technical Systems. The monitoring metrics cited below should 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

Design Time Attributes:

  • Timeframe Source: Read Timeframe from GP Attributes or Specify custom Timeframe
  • Last n Days: Value used only if Timeframe Source is set to Read Timeframe from GP Attributes
  • Select the Graphic type: Selct output type: Column chart, line chart or Table.
  • Use extended rating: Check the flag if Extended Rating Rules are used for this activity

Data Source:

  • Data is retrieved from system monitoring.
  • The metrics HTTP Response Time, HTTPS Response Time and DIALOG Response Timeare taken into account.

Output Result:

  • Charts: The output result is table, column or line chart depending on the graph type selection on design time.
  • Logs:
    • Error (Red): No Performance data found for task type HTTP for Timeframe <xxx> in UDM Store
    • Error (Red): Error occured when calling the method IF_GPCR_DATA_PROV-GET_DATA
    • Error (Red): Average response time for task type Dialog was higher then <Red Threshold> on at least one Day
    • Warning (Yellow): Average response time for task type Dialog was higher then <Yellow Threshold> on at least one Day
    • Success (Green): Average response time for task type HTTPS was below threshold on all days

Possible Errors:

No performance data for task type HTTP for timeframe <xxx> in UDM Store

Purpose: This health check may be used to check IDoc in Error State from the managed system. Different attributes are available to filter and classify the IDocs. A direct link is available to jump to transaction DB87.

Prerequisites: This plugin is only for ABAP technical 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 to Read Timeframe from GP Attributes.
  • Select the Graphic type: Graphic type display in the output report: Bar Chart or Table
  • IDoc direction:
    • Inbound
    • Outbound
    • Inbound and Outbound 
  • Threshold for Red IDoc Status: Check if the number of IDoc categorized as Red is exceeding the given red threshold, in this case a log is written and the activity is rated as red.
  • Threshold for Yellow IDoc Status: Check if the number of IDoc categorized as Yellow is exceeding the given yellow threshold, in this case a log is written and the activity is rated as yellow.
  • Codes for Green IDoc Status: Codes used to classify the IDoc in green status (Multiple codes should be separated by comma: eg:51,52,53)
  • Codes for Red IDoc Status: Codes used to classify the IDoc in red status (Multiple codes should be separated by comma: eg:51,52,53)
  • Codes for Yellow IDoc Status: Codes used to classify the IDoc in yellow status (Multiple codes should be separated by comma: eg:51,52,53)
  • Messages Types: IDoc Message type to be considered.
  • Clients: Clients to be considered when reading the IDoc

Data Source: Data is retrieved using the RFC source

Output Result:

  • Charts: Table with Client, Message Type, Satatus Code, Number of Updated IDocs, State
  • Logs: 
    • Success (Green):
    • Warning (Yellow): x IDoc messages with incomplete processing state detected
    • Error (Red): x IDoc messages in error state detected

Possible Errors: No Data Found

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

The main used case for this plugin is to allow an operator to check that the ABAP 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 ABAP Instance Availability was successful.

Prerequisites: 

  • This plugin works only for ABAP systems.
  • The monitoring metrics cited below should be active for the current scope:
    • ABAP_INSTANCE_STATUS
    • ABAP_INSTANCE_LOCAL_HTTP_AVAIL
    • ABAP_LOCAL_RFC_AVAILABILITY
    • ABAP_LOCAL_LOGON_TEST

Design Time Attributes:

  • Check "Instance Local RFC Avzailability"
  • Check "Instance Local HTTP Availability"
  • Check "Instance Status from SAPSTARTSRV"
  • Check"Instance Local LOGON TEST"

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

Output Result:

  • Charts: Table shows the System ID, the Instance Name, the Metric Name, the status, Message, Measured at <Timestamp>
  • Logs: 
  • Success (Green): System is not available via HTTP due to planned downtime
  • Success (Green): No check selected
  • Success (Green): All instance are available
  • Warning (Yellow): Could not retrieve availability status for all instance
  • Error (Red): System is not configured for monitoring
  • Error (Red): Problems with instance availability detected

Possible Errors: 

Metrics are not active for scope: Could not retrieve metric details. Instance <Inst> is not available via <Inst_Avail> Ping to <EventName>

No Metric were selected at the design time: No Check Selected

Selected scope is not an ABAP system: Activity System Availability can only be executed on ABAP Systems

Purpose: This activity plugin checks on Lock entries for ABAP managed systems.

It performs actually two kind of checks:

  • Checks users holding high number of lock entries
  • Checks old lock entries exceeding a threshold in hour.

Prerequisites: This plugin works only for ABAP Systems

Design Time Attributes:

  • Red Threshold for old entries (in hour): Default 24 Hours
  • Red Threshold for number of entries per user: Default 10000 entries
  • Check Mode: Check users holding high number of locks  and check old lock entries.

Data Source: Lock Entries are retrieved using the RFC Data Provider

Output Result:

  • Charts: the Table shows the High number of lock entries per user and number of lock entries
  • Logs:
    • Success (Green): No lock entries found older then <number of hours> hours. No lock entries found that are older than the specified number of hours.
    • Error (Red): <Number of users> hold more than <number of entries> lock entries. Check on maximum allowed lock entries
    • Error (Red): Activity Buffers Statistics can only be executer on ABAP Systems

Possible Errors:

Purpose: This activity plugin checks if runtime of active jobs from the managed system are not exceeding a given runtime threshold.

Prerequisites: This plugin works only for ABAP systems

Design Time Attributes:

  • Report only batch jobs running for longer then minutes: Threshold for runtime, the input value should be an integer value and must ends with time unit "d" or "h" or "m", default value is 60x24 minutes.
  • Select the grphic type: Bar Chart or Table

Data Source: Related Long Running jobs are retrieved using the RFC Data Provider.

Output Result:

  • Charts: The table shows the Jobname and the Runtime in minutes. The Bar Chart Output displays the Active Jobs given the runtime in minutes.
  • Logs:
    • Success (Green): No batch jobs running longer than <runtime> minutes detected.
    • Error (Red): <N> batch jobs running longer than <runtime> minutes detected.
    • Error (Red): No data retrieved. Call to data provider /SDF/CL_GPCR_CHECK_ACTIVE_JOB failed with error: <error message>
    • Error (red): Activity Long Running Jobs can only be executed on ABAP systyems.

Purpose: This activity plugin performs two types of checks on ABAP managed technical system:

  • Check for long running work processes
  • Check for work processes status (in PRIV mode)

Prerequisites: This plugin works only for ABAP systems

Design Time Attributes:

  • Enter yellow threshold for Tasktype Dialog Work Process runtime (in second)
  • Enter Red threshold for Tasktype Dialog Work Process runtime (in second)
  • Enter Yellow threshold for Tasktype Batch (in second)
  • Enter Red threshold for Tasktype Batch (in second)
  • Check Long running work processes: Threshold defined above
  • Check work processes status: Flag to check work process status (PRIV mode).

Data Source: Related Long Running Work Process are retrieve using SAPControl Data Provider

Output Result: 

  • Charts: The table shows the Task Type, Instance, Work Process Numer, Status, Time, program name and the Rating
  • Logs:
    • Success (Green): No long running dialog work processs detected on instance <Instance Name>
    • Success (Green): No long running batch work processes detected on instance <Instance Name>
    • Success (Green): No dialog work processes in priv mode detected on instance <Instance Name>
    • Warning (Yellow): <Number of dialog> work processes are running longer than <N> seconds on instance <Instance Name>
    • Error (Red): <Number of dialog> work processes are running longer than <N> seconds on instance <Instance Name>
    • Error (Red): Activity Long Running Work Processes can only be executed on ABAP systems.

 

 

 

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 displzy 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 pecific attribute.

Output Result:

  • Charts: The table shows the Component name, the Runtime Errors, the Program name and the Occurence of the dumps. !the bar chart show the Top <N> shortdumps per number of occurences. 
  • Logs: 
    • Information:<N> Shortdumps occured 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 fornumber 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 successfull 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 Occurence 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-bompliant 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 Databse 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 outout, 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, Disstatus, 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 exixts
    • 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 timerange
  • 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 uage 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 hagh
    • 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 Phisical Memory Usage (%) over a given timeframe.
  • 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 occured 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 (%), Satatus.
  • 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 occured when calling LR8GPD8HOST -> GET_DATA() usually because of bad RFC connection to Host.
    • Error (Red): 15 OS Processes with more than 0.1% CPU Cinsumption 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: This activity plugin may be used to retrieve and scan log error produced by SAP ASE Database in default file /$SYBASE/$SYBASE_ASE/install/server_name.log. The plugin allows to customize the location of the log file.

Prerequisites: This plugin works only for systems that contains SYBASE DB

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 GP Attributes
    • specify Custom timeframe
  • Timeframe: Value used only if Timeframe Source is set to 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.
  • Log file root directory: Root directory of the location of the log file, existing directory should be used here.
  • Log file path: Relative path of the location of the log file, wildcard characters can be used. example: ${SID}/ASE-*/install/${SID}.log
  • Report User Errors: Report Users Error (Severity between 10 and 16).
  • Report Internal Errors: Report Insufficient Resources and Internal errors (Severity 17 and 18).
  • Report Fatal Errors: Report Fatal Errors (Severity between 19 and 26).

Data Source: Get data fromlog File

Output Result:

  • Charts: Table shows the Severity, Error number, State and Message
  • Logs:
  • Success (Green): No error log message were detected in the ASE error log
  • Warning (Yellow): <x> Error log messages were detected in the ASE error log
  • Warning (Yellow): No ASE Error Log file found in /sybase/FBT/ASES-*/install/FBT.LOG
  • Error (Red): <x> Error log messages were detected in the ASE error log
  • Error (Red): No current monitoring metrics for ASE Free Data Space / ASE Log Space found

Possible Errors: Missing mandatory parameters

Purpose: This activity plugin may be used to check 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. TheJob 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: This activity plugin may be used to check long running processes of the SAP ASE Database from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the long running processes of the sybase database is < than 90%

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. Long running processes of the Sybase ASE Database metrics name are taken into consideration

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 leat one Databse 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 benn 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

Alert Handling Activity Plugins (FP3)

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, Disstatus, 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

Possible Errors: No instance / host defined for the used managed scope (technical system or database).

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: None

Data Source: Data is retrieved from Alert Management

Output Result:

  • Table Chart: Matric Name, First, Worst, Last, Min, Max, Last Value, Last Text
  • Bar Chart: None
  • Logs:
    • Success: The Current rating of the alert is Green depending on rating.
    • Error: The Current rating of the alert is Red / Yellow depending on rating.

Possible Errors: None

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.

Possible Errors: No physical hosts detected.

Automatic Activity Plugins

Purpose: Display the number of executed Guided Procedures were executed in the time frame

Prerequisites: The guided procedure must have as attributes:

  • LAST_N_DAYS: the last n days of timeframe
  • TOPN: the last top n number of error message

Design Time Attributes: None

Data Source: Data is retrieved from tables:

  • AGSSISE_GP_RUN: this table contains all GP instances created with latest status – create timestamp/user – last changed timestamp/user.
  • Only GP ID is available – in order to get GP information, it is necessary to access 2 additional tables
  • AGS_GPA_APPL: for GP information (design time)
  • AGS_GPA_APPL_T: For GP name (translate table for AGS_GPA_APPL).

Output Result:

  • Table Chart: The last GP execution status, GP name, Number of Executed GP Instance
  • Bar Chart: None
  • Logs Success (Green): <x> Guided Procedure were executed in the timeframe from <start date> to <end date>

Possible Errors: None

Purpose: Display the top n aborted jobs with the ABAP reports PR_GPA_EXEC_planner, PR_GPA_EXEC_job, PR_AGS_SISE_DEL_INST_LOGS.

Prerequisites: Jobs are currently running and were started in the period from last n days to now.

Design Time Attributes: None

Data Source: Read all jobs with canceled running within the ABAP reports PR_GPA_EXEC_planner, PR_GPA_EXEC_job, PR_AGS_SISE_DEL_INST_LOGS.

Output Result:

  • Table Chart: Aborted Job Name, Executed ABAP report name, Duration (s), Start timestanp, End timestamp, Status.
  • Bar Chart: None
  • Logs  (Error): <> canceled GPAjobs found in the time frame from <start timestamp> to <end timestamp>

Possible Errors: None

Purpose: Display all dumps from ST22 which occurred in the time frame from last n days to now for the batch user.

Prerequisites: The guided procedure must have as attributes:

  • LAST_N_DAYS: the last n days of timeframe
  • TOPN: the last top n number of error message
  • Batch user

Design Time Attributes: None

Data Source: Read locally all dumps from ST22 which occurred in the time frame from last n days to now for the batch user.

Output Result:

  • Table Chart: Name of dump, Object Name that raise the dump, Timestamp of the dump.
  • Bar Chart: None
  • Logs:
    • Success (Green): No dump found in the time frame from <start timestamp> to <end timestamp>
    • Error (Red): <x> Dumps found in the timeframe from <start timestamp> to <end timestamp>

Possible Errors: None

Purpose: Display the number of different error log messages were logged in the time frame.

Prerequisites: The guided procedure must have as attributes:

  • LAST_N_DAYS: the last n days of timeframe
  • BATCH_USER: the name of user
  • TOPN: the last top n number of error message
  • ERROR_PATTERN1 – ERROR_PATTERN20: different error messages format

Design Time Attributes: None

Data Source: Data is retrieved from the table AGSSISE_LOG.

Output Result:

  • Table Chart: The Error Message text, Number of Error Messages Occurence.
  • Bar Chart: None
  • Logs (Success): Info <nb> different error log messages were logged in the time frame from <Start Date> to <End Date>.

Possible Errors: None

Purpose: Display the top n long running duration with the ABAP reports PR_GPA_EXEC_planner, PR_GPA_EXEC_job, PR_AGS_SISE_DEL_INST_LOGS which are currently running and which were started in the time frame from last n days to now.

Prerequisites: Jobs are currently running and were started in the period from last n days to now.

Design Time Attributes: None

Data Source: Read the top n long running duration with the ABAP reports PR_GPA_EXEC_planner, PR_GPA_EXEC_job, PR_AGS_SISE_DEL_INST_LOGS.

Output Result:

  • Table Chart: Job name, Report name, Duration (s), Start Timestamp, End Timestamp, Status.
  • Bar Chart: None
  • Logs: Success (Green): <x> Jobs found: longest runtime was <x>seconds from <Start date> to <End date>

Possible Errors: None

Purpose: Display the size on disk locally on solution manager system for the GPA tables.

Prerequisites: the local size is calculated for those table:

  • AGS_SISE_DIR
  • AGSSISE_LOG 
  • AGSSISESCOPERUNT
  • AGS_INST_LANDOB 
  • AGSSISE_GP_RUN 
  • AGSSISE_GS 
  • AGSSISE_GS_MAP

Design Time Attributes: None

Data Source: Read the GPA table locally on Focused Run system.

Output Result:

  • Table Chart: Table name, Size on Disk (MB), Current total memory consumption (MB), Rows (Number of records)
  • Bar Chart: None
  • Logs: Success (Green), Info: Review the table size

Possible Errors: None

Health Check Plugins

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 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 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 Occurence 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 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 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 successfull 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 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 fornumber 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 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 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 displzy 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 pecific attribute.

Output Result:

  • Charts: The table shows the Component name, the Runtime Errors, the Program name and the Occurence of the dumps. !the bar chart show the Top <N> shortdumps per number of occurences. 
  • Logs: 
    • Information:<N> Shortdumps occured 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 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 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 performs two types of checks on ABAP managed technical system:

  • Check for long running work processes
  • Check for work processes status (in PRIV mode)

Prerequisites: This plugin works only for ABAP systems

Design Time Attributes:

  • Enter yellow threshold for Tasktype Dialog Work Process runtime (in second)
  • Enter Red threshold for Tasktype Dialog Work Process runtime (in second)
  • Enter Yellow threshold for Tasktype Batch (in second)
  • Enter Red threshold for Tasktype Batch (in second)
  • Check Long running work processes: Threshold defined above
  • Check work processes status: Flag to check work process status (PRIV mode).

Data Source: Related Long Running Work Process are retrieve using SAPControl Data Provider

Output Result: 

  • Charts: The table shows the Task Type, Instance, Work Process Numer, Status, Time, program name and the Rating
  • Logs:
    • Success (Green): No long running dialog work processs detected on instance <Instance Name>
    • Success (Green): No long running batch work processes detected on instance <Instance Name>
    • Success (Green): No dialog work processes in priv mode detected on instance <Instance Name>
    • Warning (Yellow): <Number of dialog> work processes are running longer than <N> seconds on instance <Instance Name>
    • Error (Red): <Number of dialog> work processes are running longer than <N> seconds on instance <Instance Name>
    • Error (Red): Activity Long Running Work Processes can only be executed on ABAP systems.

 

 

 

Purpose: This activity plugin checks if runtime of active jobs from the managed system are not exceeding a given runtime threshold.

Prerequisites: This plugin works only for ABAP systems

Design Time Attributes:

  • Report only batch jobs running for longer then minutes: Threshold for runtime, the input value should be an integer value and must ends with time unit "d" or "h" or "m", default value is 60x24 minutes.
  • Select the grphic type: Bar Chart or Table

Data Source: Related Long Running jobs are retrieved using the RFC Data Provider.

Output Result:

  • Charts: The table shows the Jobname and the Runtime in minutes. The Bar Chart Output displays the Active Jobs given the runtime in minutes.
  • Logs:
    • Success (Green): No batch jobs running longer than <runtime> minutes detected.
    • Error (Red): <N> batch jobs running longer than <runtime> minutes detected.
    • Error (Red): No data retrieved. Call to data provider /SDF/CL_GPCR_CHECK_ACTIVE_JOB failed with error: <error message>
    • Error (red): Activity Long Running Jobs can only be executed on ABAP systyems.

Purpose: This activity plugin checks on Lock entries for ABAP managed systems.

It performs actually two kind of checks:

  • Checks users holding high number of lock entries
  • Checks old lock entries exceeding a threshold in hour.

Prerequisites: This plugin works only for ABAP Systems

Design Time Attributes:

  • Red Threshold for old entries (in hour): Default 24 Hours
  • Red Threshold for number of entries per user: Default 10000 entries
  • Check Mode: Check users holding high number of locks  and check old lock entries.

Data Source: Lock Entries are retrieved using the RFC Data Provider

Output Result:

  • Charts: the Table shows the High number of lock entries per user and number of lock entries
  • Logs:
    • Success (Green): No lock entries found older then <number of hours> hours. No lock entries found that are older than the specified number of hours.
    • Error (Red): <Number of users> hold more than <number of entries> lock entries. Check on maximum allowed lock entries
    • Error (Red): Activity Buffers Statistics can only be executer on ABAP Systems

Possible Errors:

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

Prerequisites:

  • This plugin works only for ABAP systems.
  • Needed authorization object: S_ADMIN_FCD with field STOR

Design Time Attributes:

  • Red threshold for Hit Ration % below
  • Red threshold for SWAPS exceeding

Data Source: Buffer's data is retrieved using the RFC Data Provider.

Output Result:

  • Charts: Thes Table shows the Instance name, the Buffer name, the Hit ratio and Swaps.
  • Logs:
    • Success (Green): no problem with buffer detected, each buffer's Hit Ratio is not below a given value and Swap is not exceeding a given value.
    • Error (Red): Buffers with low Hitratio or Buffer sawps detected. At least one buffer whose hit ratio is below the given <Red Threshold for Hit Ratio % below> or whose swaps is exceeding the given <Red Threshold for Swaps exceeding> detected.
    • Error (Red): No data retrieved. Call to data provider /SDF/E2E_BUFFER_INFO failed with error: <error_message>
    • Error (Red): Activity Buffers Statistics can only be executed on ABAP systems.

Purpose: This activity plugin checks system license's status.

It also reminds if the status will be overdue in a number of days you specify.

Prerequisites: This plugin works only for ABAP systems

Design Time Attributes:

  • Threshold for Red rating: remaining days from today to the date when license overdue.
  • Threshold for Yelow rating: remaining days from today to the date when license overdue.

Data Source: License data is retrieved using the RFC Data Provider.

Output Result:

  • Charts: The table shows the System ID, the Product ID, the Licence Key, the Expiry Date and the Validity Status
  • Logs:
  • Success (Green): All licenses are Valid
  • Success (Green): No license found
  • Warning (Yellow): License <license key> will expire on <expiry date>. The number of days from now to expiration date is less than the yellow threshold.
  • Error (Red): License <license key> will expire on <expiry date>. The number of days from now to expirationdate is less than the red threshold.
  • Error (Red): License <license key> has expired.
  • Error (Red): Activity Active License can only be executed on ABAP systems.

Purpose: This activity plugin checks Aborted Jobs on ABAP Technical System.

It retrieves all aborted jobs for the given timeframe and group them per job name.

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 to Read Timeframe from GP Attributes.
  • Graphic type: select the desired Graphic Type (Table pr Bar Chart)
  • Use extended filters: Check if Extended Filters are used for this activity

Data Source: Related aborted jobs are retrieved using the RFC Data Provider.

Output Result:

  • Charts: The Table shows the Job Name and the number of aborted Jobs. The Graphic shows the Top 10 Aborted jobs.
  • Logs
  • Success (Green): No Job canceled between <Start Time> and <End Time>.
  • Error (Red): <number> jobs canceled between <Start Time> and <End Time>.
  • Error (Red): Activity Aborted Jobs can only be executed on ABAP systems.

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

The main used case for this plugin is to allow an operator to check that the ABAP 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 ABAP Instance Availability was successful.

Prerequisites: 

  • This plugin works only for ABAP systems.
  • The monitoring metrics cited below should be active for the current scope:
    • ABAP_INSTANCE_STATUS
    • ABAP_INSTANCE_LOCAL_HTTP_AVAIL
    • ABAP_LOCAL_RFC_AVAILABILITY
    • ABAP_LOCAL_LOGON_TEST

Design Time Attributes:

  • Check "Instance Local RFC Avzailability"
  • Check "Instance Local HTTP Availability"
  • Check "Instance Status from SAPSTARTSRV"
  • Check"Instance Local LOGON TEST"

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

Output Result:

  • Charts: Table shows the System ID, the Instance Name, the Metric Name, the status, Message, Measured at <Timestamp>
  • Logs: 
  • Success (Green): System is not available via HTTP due to planned downtime
  • Success (Green): No check selected
  • Success (Green): All instance are available
  • Warning (Yellow): Could not retrieve availability status for all instance
  • Error (Red): System is not configured for monitoring
  • Error (Red): Problems with instance availability detected

Possible Errors: 

Metrics are not active for scope: Could not retrieve metric details. Instance <Inst> is not available via <Inst_Avail> Ping to <EventName>

No Metric were selected at the design time: No Check Selected

Selected scope is not an ABAP system: Activity System Availability can only be executed on ABAP Systems

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 may be used to check Dialog and HTTP Response Time from the System Monitoring metric data for the selected ABAP technical system:

Data are displayed within a graphic. Threshold can be defined for each Response Time Category

Prerequisites: This plugin is only for ABAP Technical Systems. The monitoring metrics cited below should 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

Design Time Attributes:

  • Timeframe Source: Read Timeframe from GP Attributes or Specify custom Timeframe
  • Last n Days: Value used only if Timeframe Source is set to Read Timeframe from GP Attributes
  • Select the Graphic type: Selct output type: Column chart, line chart or Table.
  • Use extended rating: Check the flag if Extended Rating Rules are used for this activity

Data Source:

  • Data is retrieved from system monitoring.
  • The metrics HTTP Response Time, HTTPS Response Time and DIALOG Response Timeare taken into account.

Output Result:

  • Charts: The output result is table, column or line chart depending on the graph type selection on design time.
  • Logs:
    • Error (Red): No Performance data found for task type HTTP for Timeframe <xxx> in UDM Store
    • Error (Red): Error occured when calling the method IF_GPCR_DATA_PROV-GET_DATA
    • Error (Red): Average response time for task type Dialog was higher then <Red Threshold> on at least one Day
    • Warning (Yellow): Average response time for task type Dialog was higher then <Yellow Threshold> on at least one Day
    • Success (Green): Average response time for task type HTTPS was below threshold on all days

Possible Errors:

No performance data for task type HTTP for timeframe <xxx> in UDM Store

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 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 health check may be used to check IDoc in Error State from the managed system. Different attributes are available to filter and classify the IDocs. A direct link is available to jump to transaction DB87.

Prerequisites: This plugin is only for ABAP technical 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 to Read Timeframe from GP Attributes.
  • Select the Graphic type: Graphic type display in the output report: Bar Chart or Table
  • IDoc direction:
    • Inbound
    • Outbound
    • Inbound and Outbound 
  • Threshold for Red IDoc Status: Check if the number of IDoc categorized as Red is exceeding the given red threshold, in this case a log is written and the activity is rated as red.
  • Threshold for Yellow IDoc Status: Check if the number of IDoc categorized as Yellow is exceeding the given yellow threshold, in this case a log is written and the activity is rated as yellow.
  • Codes for Green IDoc Status: Codes used to classify the IDoc in green status (Multiple codes should be separated by comma: eg:51,52,53)
  • Codes for Red IDoc Status: Codes used to classify the IDoc in red status (Multiple codes should be separated by comma: eg:51,52,53)
  • Codes for Yellow IDoc Status: Codes used to classify the IDoc in yellow status (Multiple codes should be separated by comma: eg:51,52,53)
  • Messages Types: IDoc Message type to be considered.
  • Clients: Clients to be considered when reading the IDoc

Data Source: Data is retrieved using the RFC source

Output Result:

  • Charts: Table with Client, Message Type, Satatus Code, Number of Updated IDocs, State
  • Logs: 
    • Success (Green):
    • Warning (Yellow): x IDoc messages with incomplete processing state detected
    • Error (Red): x IDoc messages in error state detected

Possible Errors: No Data Found

Purpose: This activity plugin perform check on Client 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: The Activity plugin is configured via design time attributes selection:

Optional Check: CATT and eCATT Authorization, CATT and eCATT Not Allowed.

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

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

Output Result:

  • Charts: None
  • Logs: 
    • Error (Red): Client change settings of productive client 200 allows modifications
    • 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

Possible Errors:

  • There are no clients on the CCDB Store
  • There are no productive client role

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: 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 outout, 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 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 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 timerange
  • 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 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 exixts
    • 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 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 Phisical Memory Usage (%) over a given timeframe.
  • 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 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 uage 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 hagh
    • 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 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 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 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 occured 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 (%), Satatus.
  • 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 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 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 occured when calling LR8GPD8HOST -> GET_DATA() usually because of bad RFC connection to Host.
    • Error (Red): 15 OS Processes with more than 0.1% CPU Cinsumption 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 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 leat one Databse is above 0 %.

Purpose: This activity plugin may be used to check 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. TheJob 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: This activity plugin may be used to check long running processes of the SAP ASE Database from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the long running processes of the sybase database is < than 90%

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. Long running processes of the Sybase ASE Database metrics name are taken into consideration

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 retrieve and scan log error produced by SAP ASE Database in default file /$SYBASE/$SYBASE_ASE/install/server_name.log. The plugin allows to customize the location of the log file.

Prerequisites: This plugin works only for systems that contains SYBASE DB

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 GP Attributes
    • specify Custom timeframe
  • Timeframe: Value used only if Timeframe Source is set to 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.
  • Log file root directory: Root directory of the location of the log file, existing directory should be used here.
  • Log file path: Relative path of the location of the log file, wildcard characters can be used. example: ${SID}/ASE-*/install/${SID}.log
  • Report User Errors: Report Users Error (Severity between 10 and 16).
  • Report Internal Errors: Report Insufficient Resources and Internal errors (Severity 17 and 18).
  • Report Fatal Errors: Report Fatal Errors (Severity between 19 and 26).

Data Source: Get data fromlog File

Output Result:

  • Charts: Table shows the Severity, Error number, State and Message
  • Logs:
  • Success (Green): No error log message were detected in the ASE error log
  • Warning (Yellow): <x> Error log messages were detected in the ASE error log
  • Warning (Yellow): No ASE Error Log file found in /sybase/FBT/ASES-*/install/FBT.LOG
  • Error (Red): <x> Error log messages were detected in the ASE error log
  • Error (Red): No current monitoring metrics for ASE Free Data Space / ASE Log Space found

Possible Errors: Missing mandatory parameters

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>