Open Component Monitoring

This application supports Advanced System Management by providing additional monitoring metrics that go beyond standard system monitoring. Use Open Component Monitoring when configuration vastly differs between managed objects.

Open Component Monitoring supports the following metrics:

Metric Description
URL Availability This metric will measure the availability of a URL. The URL is called from the central Simple Diagnostic Agent of the customer network. The URL Availability is checked every minute.
URL Certificates Measure the remaining validity (in days) of a SSL certificate. The certificate is evaluated by calling the https URL and reading the expiration date from the response header. The URL is called from a central Simple Diagnostic Agent in the customer network.
Host Availability Measure the availability of a host. The central Simple Diagnostic Agent of the custom performs an ICMP ping to the configured host name or IP address.
TCP Port Availability Measure the availability of a TCP port. The central Simple Diagnostic Agent of the custom network performs a TCP ping to the port on the host name or IP address.
OS Processes Availability Measure if a OS Process is running on a host. This is measured by the local Simple Diagnostic Agent of the host.
Windows Services Availability Measure the status of a Windows Service. This is measured by the local Simple Diagnostic Agent of the host.

Configuration

Activate Customer Network

Many Open Component Monitoring metrics are un-modeled, which means that they are not assigned to a specific technical system in the landscape. Nevertheless, they need to be executed by a Simple Diagnostic Agent, which needs to be located inside the customer network. Therefore, it is necessary as a first step to define a central Simple Diagnostic Agent in the customer network which should execute the Open Component Monitoring metrics.

Proceed as follow to activate a customer network

  • Click the “Configuration” button in the top right corner of the Open Component Monitoring application
  • Open the area “Customer Networks”
  • You can see all customer networks in scope and their status. Click on the switch next to the customer network to activate it.
  • Select the Simple Diagnostic Agent which should be used for Open Component Monitoring and click on “Save”
  • The customer network is now active and can be used for Open Component Monitoring
  • Remark: You can click on the “Edit” button to assign another Simple Diagnostic Agent if necessary.

Create new metrics

Perform the following steps to create a new Open Component Monitoring metric:

  • Click the “Configuration” button in the top right corner of the Open Component Monitoring application
  • Open the area “Metrics”
  • Click the “Edit” button next to the metric type (e.g. “URL Availability”)
  • The table shows all existing metrics. Click on “Add Metric” to define a new metric.
  • Maintain the metric and alert attributes (see table below for common parameter descriptions)
  • Click "Save"
  • Your metric is now active and will become visible in the Open Component Monitoring application.

Here is a list of the common metric parameters to be used in Open Component Monitoring. There are additional metric specific parameters which are described in the respective chapters below.

Field Description
Metric Name Maintain a descriptive name for the metric
Customer Network Select the customer network
Collection Interval Defines how often the metric is collected
Threshold Define the metric threshold.
Metric Documentation Here you can provide additional documentation of the metric.
Alert Active Trigger an alert when the metric fails
Alert Name Maintain the name of the alert
Severity Severity of the alert in AEM. Mantain a value between 0 (very low) and 9 (very high)
Notification (optional) Select a notification variant if you want to send an additional email for the alert
Outbound Connector (optional) Select an outbound connector variant if you want to forward the alert via BAdI implementation

URL Availability

This metric will measure the availability of a URL. The URL is called from the central Simple Diagnostic Agent of the customer network. The URL Availability is checked every minute.

URL Availability metrics have the following additional parameters:

Field Description
URL

Maintain the URL

Proxy URL (optional) 

Maintain the additional proxy URL if the URL is outside your customer network. 

URL Certificates

Measure the remaining validity (in days) of an SSL certificate. The certificate is evaluated by calling the https URL and reading the expiration date from the response header. The URL is called from a central Simple Diagnostic Agent in the customer network.

URL Certificate metrics have the following additional parameters:

Field Description
URL

Maintain the URL

Proxy URL (optional) 

Maintain the additional proxy URL if the URL is outside your customer network. 

Host Availability

Measure the availability of a host. The central Simple Diagnostic Agent of the custom performs an ICMP ping to the configured host name or IP address.

Host Availability metrics have the following additional parameters:

Field Description
Hostname Maintain the host name or IP address

TCP Port Availability

Measure the availability of a TCP port. The central Simple Diagnostic Agent of the custom network performs a TCP ping to the port on the host name or IP address.

TCP Port Availability metrics have the following additional parameters:

Field Description
Hostname / Port Maintain the host name (or IP address) and the port number. This needs to be maintained in the format <hostname>:<port>

Windows Service

Measure the status of a Windows Service. This is measured by the local Simple Diagnostic Agent of the host.

Windows Service metrics have the following additional parameters:

Field Description
Service Name Maintain the name of the Windows Service you want to monitor.
Host Name The name of the host where the Windows Service should be monitored. You can select from a list of all Windows hosts in the customer network

OS Process

Measure if a OS Process is running on a host. This is measured by the local Simple Diagnostic Agent of the host.

OS Process metrics have the following additional parameters:

Field Description
Process Name Name of the OS Process. This parameter needs to be maintained as a regular expression.
User Name of the OS User. Leave this field empty to monitor processes from all users. This parameter needs to be maintained as a regular expression.
Command Line Full command line of the process. This also contain the command line parameters of the process. This parameter needs to be maintained as a regular expression.
Host Name The name of the host where the Windows Service should be monitored. You can select from a list of all Windows hosts in the customer network

Configuration (FRUN 1)

Activate Customer Network

Many Open Component Monitoring metrics are un-modeled, which means that they are not assigned to a specific technical system in the landscape. Nevertheless, they need to be executed by a Simple Diagnostic Agent, which needs to be located inside the customer network. Therefore, it is necessary as a first step to define a central Simple Diagnostic Agent in the customer network which should execute the Open Component Monitoring metrics.

Proceed as follow to activate a customer network

  • Select the application “Open Component Monitoring – Configuration” from the Launchpad (Transaction: FRUN)
  • Click “Customer Network Monitoring”
  • Select the tab “Agent Assignment”
  • Select a customer network in the table and click “Assign”
  • You can now search and display the Simple Diagnostic Agents in the customer network
  • Select the Simple Diagnostic Agent which should be used for Open Component Monitoring
  • Click on “Save”

URL Availability

This metric will measure the availability of a URL. The URL is called from the central Simple Diagnostic Agent of the customer network. The URL Availability is checked every minute.

How to create a URL Availability metric

  • Select the application “Open Component Monitoring – Configuration” from the Launchpad (Transaction: FRUN)
  • Click “Customer Network Monitoring”
  • Select the tab “Metric Configuration”
  • Click on “Add” … “URL Availability”
  • Maintain the metric and alert attributes:

Field Description
Managed Object Name Select the customer network
URL Maintain the URL 
Proxy URL  (optional) Maintain the additional proxy URL if the URL is outside your customer network. This field is only available as of FRUN 1.0 FP3.
Threshold Define the metric threshold. The recommended threshold for URL Availability metrics is "Already Rated (Best of last 3)"
Alert Active Trigger an alert when the metric fails
Alert Name Maintain the name of the alert
Severity Severity of the alert in AEM. Mantain a value between 0 (very low) and 9 (very high)
Notification (optional) Select a notification variant if you want to send an additional email for the alert
Outbound Connector (optional) Select an outbound connector variant if you want to forward the alert via BAdI implementation

  • Confirm your settings by clicking "OK" 
  • Click "Save"

Your metric is now active and will become visible in the Open Component Monitoring application.

URL Certificates

Measure the remaining validity (in days) of an SSL certificate. The certificate is evaluated by calling the https URL and reading the expiration date from the response header. The URL is called from a central Simple Diagnostic Agent in the customer network.

How to create a URL Certificate metric

  • Select the application “Open Component Monitoring – Configuration” from the Launchpad (Transaction: FRUN)
  • Click “Customer Network Monitoring”
  • Select the tab “Metric Configuration”
  • Click on “Add” … “Https Certificate Expiration”
  • Maintain the metric and alert attributes:

Field Description
Managed Object Name Select the customer network
URL Maintain the URL 
Proxy URL  (optional) Maintain the additional proxy URL if the URL is outside your customer network. This field is only available as of FRUN 1.0 FP3.
Threshold Define the metric threshold.
Alert Active Trigger an alert when the metric fails
Alert Name Maintain the name of the alert
Severity Severity of the alert in AEM. Mantain a value between 0 (very low) and 9 (very high)
Notification (optional) Select a notification variant if you want to send an additional email for the alert
Outbound Connector (optional) Select an outbound connector variant if you want to forward the alert via BAdI implementation

  • Confirm your settings by clicking "OK" 
  • Click "Save"

Your metric is now active and will become visible in the Open Component Monitoring application.

Host Availability

Measure the availability of a host. The central Simple Diagnostic Agent of the custom performs an ICMP ping to the configured host name or IP address.

How to create a Host Availability metric

  • Select the application “Open Component Monitoring – Configuration” from the Launchpad (Transaction: FRUN)
  • Click “Customer Network Monitoring”
  • Select the tab “Metric Configuration”
  • Click on “Add” … “Host Availability”
  • Maintain the metric and alert attributes:

Field Description
Managed Object Name Select the customer network
Hostname Maintain the host name or IP address
Threshold Define the metric threshold.
Alert Active Trigger an alert when the metric fails
Alert Name Maintain the name of the alert
Severity Severity of the alert in AEM. Mantain a value between 0 (very low) and 9 (very high)
Notification (optional) Select a notification variant if you want to send an additional email for the alert
Outbound Connector (optional) Select an outbound connector variant if you want to forward the alert via BAdI implementation

  • Confirm your settings by clicking "OK" 
  • Click "Save"

Your metric is now active and will become visible in the Open Component Monitoring application.

TCP Port Availability 

Measure the availability of a TCP port. The central Simple Diagnostic Agent of the custom network performs a TCP ping to the port on the host name or IP address.

How to create a TCP Port Availability metric

  • Select the application “Open Component Monitoring – Configuration” from the Launchpad (Transaction: FRUN)
  • Click “Customer Network Monitoring”
  • Select the tab “Metric Configuration”
  • Click on “Add” … “TCP Port Availability”
  • Maintain the metric and alert attributes:

Field Description
Managed Object Name Select the customer network
Hostname Maintain the host name (or IP address) and the port number. This needs to be maintained in the format <hostname>:<port>
Threshold Define the metric threshold.
Alert Active Trigger an alert when the metric fails
Alert Name Maintain the name of the alert
Severity Severity of the alert in AEM. Mantain a value between 0 (very low) and 9 (very high)
Notification (optional) Select a notification variant if you want to send an additional email for the alert
Outbound Connector (optional) Select an outbound connector variant if you want to forward the alert via BAdI implementation

  • Confirm your settings by clicking "OK" 
  • Click "Save"

Your metric is now active and will become visible in the Open Component Monitoring application.