Page tree
Skip to end of metadata
Go to start of metadata

Frequently Asked Questions for System Monitoring

The frequently asked questions are grouped in the following categories:

(lightbulb) Your Help is required!

We are constantly finding new questions in the area of System Monitoring. Therefore your feedback is important. If you have any questions which could be helpful for other visitors of this Wiki, please let us know. You can provide us feedback with the comment tab on this page.

General Questions 

You can find the list of provided monitoring templates in the Solution Manager Configuration work center (transaction SOLMAN_SETUP). They are displayed in the area "Technical Monitoring", step 3 "Template Maintenance". If you do not yet have a Solution Manager 7.1 installed, you can also find a list of supported products here.

Technically a customer has 2 options for monitoring with SAP Solution Manager 7.1

  1. The new Monitoring and Alerting Infrastructure (MAI) which was introduced with Solution Manager 7.1 (with SAP Host Agent and Diagnostic Agents). The applications are provided in the work center "Technical Monitoring".
  2. The "old" CEN based monitoring work center which was already available in earlier versions of Solution Manager (central CCMS with SAPCCMSx agents).The applications are provided in the work center "System Monitoring"

It is recommended to use the first option with SAP Solution Manager 7.1. Only with this solution you can benefit from the various new features like:

  • Central configuration and administration of monitoring infrastructure from Solution Manager
  • Automatic detection of landscape components via SLD
  • Mass maintenance of monitoring configuration with templates
  • Unified Alert Inbox
  • Integration to interactive reporting capabilities
  • Graphical monitoring applications
  • Monitoring of non-ABAP based components like for example J2EE, Business Objects, HANA, standalone databases
  • Integration to other monitoring scenarios like PI Monitoring, BI Monitoring, Connection Monitoring

This may involve some changes in the landscape (e.g. installation of Diagnostic Agents, Managed System Setup), especially for customers who have not yet enabled Root-Cause Analysis for their systems. In this case a customer can perform an upgrade to SAP Solution Manager 7.1 and still use option 2 for monitoring. The "System Monitoring" work center can still be used after the upgrade, with the same features as in Solution Manager 7.0. So it is not necessary to introduce the new monitoring infrastructure as a big bang project. However, there will not be any new features with this approach. If you want to use the features mentioned above, you should consider a switch to the new MAI.

The 2 infrastructures are completely distinct from each other.

  • It is not possible to monitor Diagnostic Agents in RZ20 (as they are not necessary for a CEN)
  • It is not possible to monitor SAPCCMSx agents from the new MAI (as they are no longer necessary there)

Here is a list of relevant support components, based on different problem areas:

Problem Area

Support Component

Managed System Setup


Diagnostic Agent


SAP Host Agent


System Monitoring Setup (e.g. Content Update, Template Maintenance, Template Assignment)


Alert Inbox application


System Monitoring application


The ratings of metrics or alerts are not calculated correctly


Metrics are not collected correctly (e.g. grey metrics)


DB2 database metrics


MaxDB database metrics


MSSQL database metrics


Oracle database metrics


Early Watch Alert





Please first check if you question is answered by the Setup and Configuration wiki for System Monitoring. 


Please check the wiki area Setup Examples for Monitoring which contains an example how to exclude file systems form monitoring. Another guide can be found in the guide Template Maintenance - File System Variants.pdf which is provided in the How-to Guides.

Please check SAP note 1738283. It contains the necessary prerequisites for the monitoring of clustered database solutions.

  1. What is the difference between “Maintain Recipient Lists” and “Maintain Global Recipients”? Recipients have to be maintained for Alerting. Only those people who have been maintained as a recipient can be assigned to receive notifications, it is not possible to send a notification to a normal SolMan User, only recipients. It is possible to maintain and assign individual Users as Recipients but also you can create a list of recipients if you have a group of people (e.g. Senior Managers) who need to be assigned to several alerts for several systems. Maintain Global Recipients is to maintain individual users and Maintain Recipient Lists is for the lists.
  2. What is the Add and Delete for? Once you have defined a Recipient or Recipient List you can assign them here to receive notifications.
  3. When I go into recipient lists or global recipients it shows me a separate listing then displayed bellowed these buttons? This is showing the available recipients or recipient lists that can be assigned.
  4. Are the distribution lists, SAP office distribution lists? I cannot see or access distribution lists, only recipient lists, can you send another screen shot?
  5. Is there documentation on the My notification settings? I cannot find anything specifically on My Notification Settings. What is not clear, do we need some documentation here?
  6. Is an activation required after changes? Once you have added a recipient or recipient list no further activation is required.

The Monitoring and Alerting Infrastructure provides the enhancement spot ALERT_REACTION where you can specify custom alert reactions. This enhancement spot and the corresponding Business Add-In (BAdI) BADI_ALERT_REACTION are described in the document "Alert Consumer BAdI Interface" on the following page: MAI_AlertInbox_Home.

This functionality can be used to trigger additional events in case of an alert like for example:

  • Calling an external web service on a 3rd party incident management tool
  • Write information to a log file
  • Execute additional OS scripts on the SAP Solution Manage

Please perform the below mentioned steps to create custom template and disable the unwanted metrics for Reporting.

  1. Launch SOLMAN_SETUP -> Technical Monitoring -> System Monitoring -> Template Maintenance.
  2. Select the SAP Template which you have assigned to managed object for monitoring.
  3. Click on Create Custom Template button.
  4. Custom template is created and shown in the display area.
  5. Click on Metrics tab.
  6. Select the Metric which is not required for reporting.
  7. On the Metric details table, select "Data Usage" tab.
  8. Deselect the check box "Send Values to SAP Netweaver Business warehouse".
  9. Click on Save button to save the changes.
  10. Navigate to Define Scope step and select the required managed object
  11. Navigate to Setup Monitoring step.
  12. Assign and apply the custom template to the managed object.

Once the auto configuration is successful, reporting for the metrics will be disabled.

If you do not want to monitor the system anymore, you can remove the system from Monitoring.

This can be done on the "Define Scope" step. Select the system (or more than one system) and click on "Remove Monitoring" button. Click on yes on the confirmation pop-up. The system won't be monitored any more and you will not receive any alerts for that system. After this, if you want to monitor the system again, re-run the configuration by clicking on "Apply and Activate" button on the Setup Monitoring step for the corresponding managed system. 

No, monitoring templates are not client-specific.

To remove the duplicate assignment, please perform the following steps.

  1.  Select the managed system in "Define Scope" step and navigate to "Setup Monitoring" step.
  2. Select the system managed system and click on "Restore Defaults" button.
  3. Once the Default is restored, the duplicate assignment will be lost.
  4. Click on Apply and Activate button to start monitoring the system with the current template assigned.

There is a way to set up notifications system-wise, this can be necessary if different support groups need to be notified for systems that use the same monitoring template.

On system-level you can use business partner functions on system level (see the Setup and Configuration wiki for details). For Technical Instances, hosts and databases this is not possible so far. For these MO types you can use MO-specific configuration to do this.

  1. In the Setup Monitoring step, after performing the auto configuration (Apply and Activate), click on "Configure Managed Object" button.
  2. The template for the selected managed object will be opened in a new window.
  3. Make the required settings on the Notifications tab of selected Alert or/and on the Notifications tab in the managed object template based on your requirement.
  4. Save the changes made and close the window.
  5. Refresh the Setup Monitoring step.
  6. MO-Specific flag for the managed object will be ticked.
  7. Click on Apply and Activate button to activate the changes made at the Managed Object level.

What ever settings you made in the Managed Object template, will be specific to the Managed Object. Likewise you can do the required configuration for all the required managed objects.

Once the Managed Specific settings are maintained, the template level settings will be ignored by run time and only Managed Object settings will be taken into consideration.

In case, you need maintain notification setting at a different level then follow the standard SAP help guide.

Starting from SP10, this functionality is available.

Please perform the following steps to activate email notification only for alerts of a particular Category.

  1. Navigate to Solman_Setup -> Technical Monitoring -> System Monitoring -> Template Maintenance step.
  2. Select the template you are planning to assign to the managed object.
  3. Select Notifications tab.
  4. Select the option Inactive for "Auto-Notifications".
  5. Select Alerts tab.
  6. Select the Alert related to the Category.
  7. Select Notifications tab on Alert Details table.
  8. Make the Auto-Notification active. Add the required recipient/recipient list IDs.
  9. Click on save button.
  10. On the Define Scope step, select the managed object required and navigate to Setup Monitoring step.
  11. Assign and apply the template to the Managed Object.

Auto Notifications will be created only for the Alerts related to a specific category.

Check the package assignment of your template on the "Template Settings" tab. Your template most likely is assigned to the package $TMP.

Custom Templates created in $TMP (Local Object) are only local to that system. They cannot be transported to any other systems.

The package assignment of a template once created can never be changed. The only solution would be to use the 'Copy Custom Template' functionality to create a copy of the custom template and assign a different package.

If the use case is to create the custom template in development system and then transport it to production system, then while creating the custom template, they should be assigned to a valid customer package.

The reason you are not able to change the template assignment for the managed Objects is, MO-Specific setting flag is ON. Meaning, there are some specific settings maintained for the managed objects specifically.

If you would like to change the template assignment, following steps  need to be followed.

  1. Select the Managed Object for which the MO-Specific flag is ON.
  2. Click on "Maintain MO-Specific settings" link. Managed Object template would be launched. 
  3. Click on Expert Mode button on Managed Object template.
  4. Ensure you are in edit mode.
  5. Click on the "Reset all settings" button.
  6. Save the changes made.
  7. On the Setup Monitoring step, click on the Refresh button.
  8. MO-Specific flag would be OFF.

Now you can change the template assignment.


The alert priority which is displayed in the Alert Inbox is calculated from the alert severity (as defined in the template) and the current alert status:

Severity / Current Rating

0 to 2

3 to 5

6 & 7

8 & 9




Very High

Very High





Very High











In the default view, the alerts in the Alert Inbox are sorted by the calculated alert priority. You can also display the defined severity of an alert in a separate column. To do this, you have to click on "Settings" -> "Column Selection" and add the column "Severity".

If the Assignment status is Yellow for the corresponding managed object on Setup Monitoring step after the Managed Object specific settings are maintained, this means that the settings you maintained at the managed object template level are not activated on the managed object.

Please select the managed object and click on Apply and Activate button for the MO specific settings to be active. Once this is done the Assignment Status and Setup Staus would turn Green for the managed object and managed object specific settings will be taken into consideration during run time.

  • Ensure that a valid email Id is available for background user who is triggering the auto-notifications.
  • Check if the user intended to receive the notification is a recipient with a valid email/SMS.
  • Check if the user intended to receive the notification is a recipient list(group) in which case check whether there are recipients in the recipient list. Please understand a recipient list is just a name of a group of recipients and only if there are recipients in it, can we send notifications.
  • Check if the user intended to receive the notification has any notification settings and they are valid(on-duty, absences, substitutes etc).
  • Check if the user intended to receive the notification has any on-Duty notification settings with factory calendar and holiday calendar mentioned. In such a case, please goto transaction SCAL and check if the calendars are upto date. If they are already expired, please refer to Note 501670(manual update) or 1426524(automatic update - Not recommended so it is Pilot release - If needed please raise a request against the component XX-CSC-XX) 

With some support packages of Solution Manager there is no template available for SAP HANA on the technical system level. But to monitor SAP HANA standalone databases you need a template on technical system level to see a valid value in the System Monitoring system list and to access the hierarchy for the HANA system.
 Perform the following steps to create a template for you SAP HANA system and turn the monitoring status green for HANA Technical System.

  1. Launch SOLMAN_SETUP -> Technical Monitoring -> Template Maintenance.
  2. Under Technical Systems select the 'Generic Product version.
  3. Create a custom template
  4. Select you SAP HANA system in step "Define Scope"
  5. Finally in step 6 "Setup Monitoring", you can then choose to 'Assign Templates' on the technical system level and from the dropdown menu next to "Generic Product Version" you can choose the custom template you just created.
  6. Then when you apply and activate the monitoring the technical system status will be aggregated from the underlying SAP HANA DB templates and displayed in the system list.

Create a technical scenario of type "workmode management". Insert all relevant systems into this scenario and schedule work modes for it.
Help link :

Common Issues  

This issue could occur if more than one ABAP instance is running on the same host.

A fix is available with

  • LMSERVICE SP3 patch3
  • LMSERVICE SP4 patch1

You have to activate additional settings in your virtualization environment. This is described in SAP note 1409604.

This can happen after a kernel update when the version of sapstartsrv is different from the kernel version. The resolution for this issue is described in SAP note 1586315.

Assign role SAP_NOTIF_ADMIN and e-mail ID to user SOLMAN_BTC. See SAP note 1581460.

Assign the role "SAP_NOTIF_ADMIN" to the user.

If you still have trouble, follow the procedure given in the link. . This is described in SAP note 1648302.

If the software components of the Product Instance you assigned during the managed system setup does not match the software components installed on the managed system, the extractors are flagged as inconsistent. This happens e.g. after the upgrade of a managed system.

• Check these software component versions (in case of ST_PI it is the software component SAP BASIS). • Check in the extractor details, the component version ID (which is the ID of the software component version).

All these versions needs to be consistent.

If any inconsistent versions are found you need to assign the correct Product Instance which includes the Software Component versions installed on the managed system.

  1. Check the Notes 1759626 has been implemented in the system
  2. After the note implementation, import the latest SP08 content (steps to import the content has been suggested in Note 1742119).
  3. After the latest content is imported and applied, use the report attached to Note 1696166 to clear any inconsistent entries.

Also for troubleshooting Technical Monitoring issues please see the Knowledge Base Articles (KBA's) below:

2184681 - How to Customise Alert Email Header in Technical Monitoring

2264627 - How to Troubleshoot Grey HANA Metrics in Technical Monitoring - SAP Solution Manager 7.1

2227586 - How to delete unwanted Managed Objects permanently from Technical Monitoring

2248060 - File System monitoring - How to exclude File Systems using Windows Regular Expression in Technical Monitoring

2202670 - File System Monitoring - How to exclude AIX/UNIX file systems using Regular Expression in Technical Monitoring

2178457 - How to troubleshoot Introscope Metrics (Enterprise Manager) in Solution Manager Technical Monitoring

2257249 - How to use File Text Pattern Search for File Monitoring in Technical Monitoring

2219816 - How to troubleshoot Notification issues in Technical Monitoring

2270160 - How to Identify Issues with the Metric Status propagated from Host, Database & Technical Instance in Technical Monitoring

2218186 - How to deactivate Automatic Incident Creation in Technical Monitoring, Solution Manager

2153218 - Responsibility of individual steps in Technical Monitoring under SOLMAN_SETUP

1875905 - How to Deactivate Earlywatch Alerts in Technical Monitoring



  • No labels

1 Comment

  1. Former Member


    Thanks for the useful info.
    Whilst setting up work modes in 7.1 SP12, I'm running into a few procedural problems.
    Here's an example:

    I currently run work modes on all systems (including DBs) for every hour of the day.

    • 00:01 - 08:59 - Non-business hours.
    • 09:00 - 10:00 - Peak business hours.
    • 10:01 - 18:00 - Normal business hours.
    • 18:01 - 23:59 - Non-business hours.

    Let's imagine that I wanted a downtime work mode from 09:45am until 10:45am (1 hour).
    Here's what I would need to do:

    • Adjust "Peak business hours" to finish at 09:44am.
    • Adjust "Normal business hours" to start at 10:46am  (this is actually optional, I could just add a 15min downtime and then "Add New Phase" to extend over existing work modes).
    • Create new downtime work mode to run from 09:45 to 10:45.

    That works well, provided that I actually use the full hour of the downtime window.
    If I decided at 10:30am that 1 hour wasn't enough, I could simply "Add New Phase" to the downtime work mode and it would overlay with the "Normal business hours" work mode (as we know, a downtime takes the priority when this happens, and monitoring is still suspended - or whatever you've configured in the MAI config).

    Now what happens if my downtime only takes 30 minutes, finishing at 10:15am?
    I have three options as follows:

    • 1 - Leave the downtime work mode in place until 10:45 as planned.
      Pros: Simple to do.
      Cons: No monitoring on that system until 10:45 - monitoring gap.
    • 2 -  Remove the downtime work mode - delete it.
      Pros: Simple to do.
      Cons: No monitoring on that system until 10:45 - monitoring gap.
    • 3 - Adjust the end of the downtime work mode. 
      Pros: Simple to do.
      Cons: No monitoring on that system until 10:45 - monitoring gap.

    So, all of the options would leave a monitoring gap (remember, the follow-on work mode doesn't start until 10:46am), unless I then go and modify the start time of the follow-on work mode "Normal business hours".
    There's a slight issue with this also, especially if you've configured metric alerting thresholds differently for different work modes.  But I won't go into this now.

    Therefore, to prevent a monitoring gap, my process now extends to:

    • Adjust "Peak business hours" to finish at 09:44am.
    • Adjust "Normal business hours" to start at 10:46am  (this is actually optional, I could just add a 15min downtime and then "Add New Phase" to extend over existing work modes).
    • Create new downtime work mode to run from 09:45 to 10:45.
    • Realise that downtime work mode window is too long, as we finish the work 30 mins early at 10:15.
    • Adjust "Normal business hours" to start at 10:16am (the next minute after 10:15).

    The above tasks would need to be done for both the SAP technical system & the database.
    That's for 1 whole system.

    What happens if I tell you that there are 2 or even 3 systems involved?
    That's a lot of effort just to manage a downtime work mode.

    I thought I had found the solution by using "Technical Scenarios".
    I thought that maybe I could assign the systems involved into a technical scenario and do all the work mode scheduling/controlling at that level.
    Then, when it comes to downtime, create a "downtime" technical scenario with the desired schedule and simply re-assign the technical systems into that scenario.

    But, it seems that work mode schedules from technical scenarios are propagated and not inherited.
    Meaning, when I delete or adjust work modes on the technical systems / databases, or when I move the technical systems between scenarios, they do not re-inherit the work modes of the parent technical scenario.  Instead they retain the ones they were originally assigned from the technical scenario where they were first created.

    And so to the question.  How can I efficiently manage work modes for multiple systems when downtime or maintenance is needed, without jeopardising the system monitoring?
    Is there another way that I'm just not seeing?

    Thanks in advance.