- Monitors the response time of ABAP instances
A versatile solution for monitoring SAP NetWeaver, SAP S/4HANA and HANA systems
A versatile solution for monitoring SAP S/4HANA and HANA systems
A versatile solution for monitoring SAP BusinessObjects®
A solution for managing the operations and the monitoring of any SAP landscape, integrated in ServiceNow
This Cockpit is a complete solution for managing the operations of any large SAP landscape and ensuring maximum performance and availability of its services. It combines the power and flexibility of the ServiceNow® service management platform with our SAP monitoring solution, Pro.Monitor.
By working from an updated SAP context, your teams will be able to handle operations with the right priority and make the right decisions as well as control operations and services from the same location.
Visualize SAP landscape status, performance and utilization with live dashboards Detect and analyze problems with fine-grained alarm and metric console
Get analysis reports on specific modules, like transactions or jobs performance Automate incident creation, assignment and resolution based on SAP alarms
Manage a team by defining members, roles, skills, on-call schedule Define workload by creating recurrent operational tasks in relation with your systems
Register and maintain automatically your systems in the CMDB
ABAP response time is one of the key metric to measure system performance as experienced by the users. It is important to detect any performance drop in order to react before too many users get impacted.
This monitor will watch for the response time of DIALOG, SPOOL and UPDATE tasks. It will also focus on specific database response time and steps rate to watch for system utilization. You can be notified with an alarm when a performance drop is detected or if system utilization increases above a limit, and constantly send those metrics to you monitoring system for dashboards or reports.
The goal of this monitor is to follow the amount of connections on each application server and to detect when the number of connected users is above a threshold. you can differentiate interactive, RFC and plugin users and apply specific threshold for a given application server.
This monitor is dedicated for surveillance of ABAP application servers (AS). It will send an alarm if an AS cannot be reached, if it is not registered on the message server or if is has been restarted.
Work processes are the actual workers in SAP. It is important to check their state, availability and run time.
This monitor will watch work processes of all kinds, with the ability to tune the monitoring for specific tasks or cases.
It will detect long running processes, stopped or private processes, compute the usage ratio, and notify as soon as a threshold on those metrics is reached.
This monitor is dedicated to the surveillance of the dispatcher queues. It can monitor the number of requests waiting in the queues at a given time, and the number of requests written within a given period of time.
This monitor will look for locks on table objects and generate alarms if too many locks are waiting since a given time
This monitor will check the following memory metrics:
This monitor will look for SAP buffers used space, hit ratio, directory used, swap rate and quality.
Hit ratio, swap rate and buffer quality metrics can be computed since the startup of the instance, or within a period of time.
A short dump is generated when a program ends unexpectedly. This is a serious indicator that something went wrong during its execution and that some business processes might be impacted.
This monitor will watch for all short dumps occurred on the system.
You can create general monitoring rules to be notified when a bursts of short dumps is detected. You can also create specific rules to cover special use cases on a given client, instance or for a given program.
This monitor is dedicated for the monitoring of spools and spool requests: Used number and size for the spools, status and waiting time for the spool requests
This monitor will check that a destination can be reached from all application servers, using either a RFC ping or an authentication, based on RFC destination configuration.
This monitor is dedicated to the monitoring of QRFC queues. It will watch for:
- Queue error status
- The number of current entries
- The number of entries older than a specified age
This monitor is dedicated to the monitoring of TRFC. It will watch for:
- The number of TRFC with a given error status
- The TRFC entries older than a given age.
You can customize the monitoring for a specific direction, destination, function/program or user.
This monitor will check the status of java instances discovered via the SAPControl protocol. If the status of any instance become unavailable, it will send an alert
This monitor will check process status as seen by the SAP management console, using the SAPControl protocol.
It will send an alarm if an expected process is not running.
This monitor will check the status of java components discovered via the SAPControl protocol. If the status of any component is in error, it will send an alert
This monitor is dedicated to the monitoring of IDOC messages. It will look for ERROR or WAITING status of messages received with a given period of time.
You can customize the monitoring by creating specific rules depending on the client, the message type, the partner and the direction.
This monitor is dedicated to surveillance of SAP background jobs. It will watch for job error status, duration, delay and job occurrence.
You can set general rule to watch any job and be notified as soon as any fails.
You can also configure specific rule for a given job to monitor its real schedule or duration.
This monitor is dedicated to the monitoring of batch inputs. It will look for batch input sessions with error status occurred within a period of time.
Notifies with an alarm when a batch input session is in error
This monitor is dedicated to the monitoring of one of the key service of the NetWeaver instance: the updates service. Sends an alarm as soon as the service is not running.
This monitor is dedicated to the monitoring of SAP updates. It will look for updates with ERROR, NOT_COMPLETED or INCONSISTENT status.
When an update or a group of updates with such status is discovered, the monitor will generate an alarm
This monitor will focus on the application logs of the system. You can monitor log entry status, as well as the messages contained in a log.
To enable the surveillance, you will have to define a list of objects and sub-objects that you want to watch.
Note:It is not possible to set filters on text messages contained in the logs, only importance and severity can be monitored.
This monitor is dedicated to the monitoring of SAP transactions average execution time per step.
You can define the transaction, task and period for which you want to analyze the response time. The monitor will then generate an alarm if the response time is over a threshold.
This monitor is dedicated to surveillance of SAP process chains BI. It will watch for execution error status, duration, delay and job occurrence. You can set general rule to watch any process chain and be notified as soon as any fails. You can also configure specific rule for a given job to monitor its real schedule or duration.
The CCMS from SAP can contain thousands of metrics and alarm configurations. It has often been widely customized and one may want to keep using its configuration.
This module has been designed to discover metrics and alarm configuration from the CCMS and to re-use it as is. Alarms generated by the CCMS can simply be detected and propagated, or CCMS configuration can be imported in Pro.Monitor and extended from there.
Generic profiles can then be created and used on many different systems, from different departments or customers, while keeping a central configuration.
This monitor will give the possibility to extend the surveillance of Java systems to additional metrics.
Java metrics naming and availability change a lot from system to system. This monitor will discover metrics from the SAP management console and let you customize how you want to monitor them.
Combined with the use of configuration templates, the visibility of the monitoring is greatly improved.
Lot's of problems can be detected by checking the system logs. This monitor gives the possibility to regularly check within a period of time if a given log pattern can be found in sys log.
When a problem is detected, you will be notified by an alarm containing the line of logs itself, or a count of lines matching the pattern.
This monitor can be very useful if you know the signature of a problem in the logs, to be notified as soon as it occurs. It can also be used to detect an abnormal number critical log lines.
Transports are used to propagate changes across systems. It is important to detect when a transport is in an error state in order to reprocess it.
This monitor will watch for failed transports and notify as soon as one is detected
If too many exclusive locks are held for a long time, performances of the whole system can be impacted. This monitor will help to watch for such situations and generate an alarm if one is detected.
HANA services are the key components of the HANA systems and must stay available. This monitor will watch for the availability and status of all HANA services
This monitor will collect the current alerts from HANA statistics engine and forward them through probe alarm interface
HANA database uses disks for persistence. To run out of disk space is to avoid at all cost to maintain the service running.
This monitor will check disk used space of the HANA database at different levels.
Memory is the main resource of HANA DB and must be watched closely. This monitor will check the memory usage of every service and notify if utilization exceeds threshold
Monitors the CPU usage of HANA database at the instance and service levels.
Merge statistics will indicate the performance of the system in persisting changes. This monitor will check for the time taken by the merge operation applied on each table to detect any performance drop in the merge operations
Operations executed on the database occur within working threads. A long running thread can potentially indicate performance or optimization issues. This monitor will look for running threads and notify when a threads runs for too long
Backups are important for disaster recovery, you have to make sure that DATA and LOG are saved regularly. This monitor will look for the time elapsed between last backup as well as backup size and duration.
To monitor table statistics is useful to detect potential performance or optimization problems. This monitor will check for the number of records and delta records as well as memory and disk usage of the column store tables.
The connections are an indicator of the database load and utilization. This monitor will watch for the number of RUNNING connections and send an alarm if too many are detected.
If too many transactions are blocked for a long time, this could indicate performance or optimization problems. This monitor will watch blocked and uncommitted transactions.
System replication in HANA is a key component to be resilient against hardware failures or data corruption.
This monitor will check that the replication system is in the expected state, during its nominal and transition phases (init,sync).
It will also check for reconnects and fail overs and notifies as soon as those situations are detected.
Log retention is important in the replication mechanism as it defines the capacity of the primary system to absorb and store changes waiting to be sent toward the secondary system. If logs are produced quicker than consumed for a long time, the replication will be compromised.
This monitor will detect those situations and send alarms so you can react before replication stops.
Log shipping statistics is important in the replication mechanism as it defines the capacity of the primary system to send changes toward the secondary system. If logs are produced quicker than sent for a long time, the replication will be compromised.
This monitor will detect those situations and send alarms so you can react before replication stops.
HANA nodes status are visible in the system and this monitor will watch for them. Send an alarm when a node is in an error state.
SAPConnect handles message sending from SAP via different media like FAX, EMAIL and PAGING. Message sending can be very important for some processes and must be monitored accordingly. This monitor will watch for messages with ERROR or WAITING status and notify when problems are found.
This monitor is dedicated to the monitoring of SAP database size.
Backups are very important in case of disaster recovery and must be monitored closely. This monitor will look for backup age, size, status and duration for Oracle, MSSQL and DB2.
Clients correct configuration is important to guaranty system integrity against changes. This monitor will check that system and clients change modes are matching the expected configuration.
This monitor is dedicated to the monitoring of PI/XI messages status of ABAP stack instances. It requires to be associated with an ABAP connector to the target SAP system
PI/XI communication channels must be monitored to detect transmission errors. This monitor will watch for channels with error status.
The goal of this monitor is to detect when a consumer cache has an error status
This monitor is dedicated to the monitoring of PI/XI messages status of Java stack instances. It will detect messages with an error status and report with alarms and metrics
The ICM allows the SAP system to communicate toward other systems and must be available at all times. This monitor will check the status of the ICM as well as utilization of connections, threads and queues.
With this monitor you will have an alert every time a server is in an unexpected state for more time than a threshold you’ve configured.
For example, you can have an alert when a server is in the state “stopped” for more than one minute. As it’s completely customizable, you can make sure that nobody activates a server that you don’t want it to be working. This monitor can also send metrics concerning the state of the servers.
Monitor to make sure that a metric (populated by business object himself) isn’t breaking a threshold you’ve configured here.
For example, you can have an alert if the concurrent number of audit events in the queues is more than 100.
Monitor to make sure that some configuration properties of you server aren’t configured with values you don’t want. For example, you can have and alert every time the log level is set to something else than “low”.
This monitor helps you to :
-Make sure that the CMC is available. As this monitor is doing the same actions as a user would do within his browser, you can increase the quality of the end user experience.
-Make sure there isn't any warning in the CMC's auditing dashboard. As this information is calculated by the CMC, the only way to check this is by doing it manually. Pro.Monitor can do this for you.
This monitor helps you to :
-Make sure that there is not a lot of users connected at the same time. You can have an alert when the number of concurrent sessions in your system is breaking a threshold. Moreover, this monitor can provide metrics that will allow you to have a chart representing the user activity in your system.
-Make sure that a user isn’t logged in your system too many times.
This monitor helps you to :
-Make sure that nobody has configured a schedule to run too often. You can have an alert when a schedule is scheduled to run underneath a threshold (in minutes) you’ve configured.
-Make sure that you don’t have too many failed schedules in your system. This allows to make sure that you are not polluted with data you won’t need anymore.
-Send an alert every time a new failure is detected for a given schedule. Plus, this monitor will send metrics for you to have a chart with the execution states of a schedule.
Once installed, you can give access to your SAP landscape directory.
All registered SAP components will be discovered and you can choose which environment will be monitored.
Choose how your systems will be monitored amongst a list of preconfigured monitoring profiles.
Customize specific use cases if needed.
You are all set!
|S/4HANA & NetWeaver||HANA DB||BusinessObjects|
|1 system per month||200 USD||150 USD||150 USD|
|Non prod 50% discount|
|3rd party plugins|
|Support & Upgrades|