Jira links. Created by Anonymous , last modified by Stephanie Daum on Jul 15, Former Member. Permalink Jun 08, Great Work, Guys!!! Permalink Dec 05, Anyone can tell me where I colud find that Guide, please Regards. Permalink Nov 17, Content Tools. The Log section shows detailed logs for every activity that was performed. Browse pages. A t tachments 0 Page History. Dashboard Home.
Jira links. Created by Michael Kloeffer on Aug 18, The automatic basic configuration is divided into a roadmap of three sections: The first section is the System Prepration. This setup prepares the system for the configuration.
When required, SAP publishes a new content. Changes in the new content version can include. New content versions are implemented using the Rapid Content Delivery. If your security policy does not allow this, it is also possible to download the content and apply it manually in your SAP Solution Manager.
When to apply a new content? There is no recommended strategy how frequently to check for a new content version and apply it. In general, content updates are not required as long as monitoring is working. A content update should be performed before starting to create custom templates for System Monitoring. You may also be asked by SAP support in a customer incident to apply the latest content.
What are possible side effects when applying a new content? The new or changed monitoring settings are not automatically active. However, whenever you activate monitoring for one or several systems, the new content version will be used for the managed objects affected. Consequently, the monitoring could theoretically behave differently than before. All changed objects, however, are not affected by the content update. You can also copy objects to the customer namespace by deliberately changing settings see the section about template maintenance below if you want to protect them against unwanted changes triggered by content updates.
A possible side effect could be that you get new alerts. Step 5: Define Scope. In this step you select the managed object you want to configure for system monitoring.
Without selecting a managed object you cannot proceed to the next setup steps. Please note that selecting a managed object and configuring monitoring in step 6 creates a so-called entry point. If you select a technical system in step 5, a corresponding entry point will be created for this technical system, and System Monitoring will be activated for all associated managed objects including technical instances, database and hosts.
This allows you to remove monitoring for the whole entry point in one go, if required. If you would select an additional managed object for the same technical system, e. Hence, it is recommended to always select the technical system on the Technical Systems tab. In particular, databases and hosts should only be selected in step 5 in the case of stand-alone databases or stand-alone hosts. Step 6: Setup Monitoring. In this step monitoring templates will be assigned to the managed systems in scope.
Each technical system is associated with several managed objects e. This hierarchy is pulled from the LMDB and displayed in step 6. Note that the assignment of managed objects to the technical system cannot be changed in step 6. If any wrong information is displayed here e. Based on the information about installed products as maintained in the LMDB, default templates are automatically assigned to the different managed objects.
The current assignment can be seen in the column Assigned Templates. The assignments can be changed per managed object and per product via Assign Templates. Only templates matching the corresponding product either the SAP delivered standard template or corresponding custom templates can be assigned. Per product, only one template can be assigned at the same time. After verifying the correct assignment of templates, click Apply and Activate to write the monitoring configuration to the directory tables and activate monitoring.
This is required after each change within an assigned template or in case the template assignment was changed. Depending on the number of selected systems, the activation may take few seconds until several minutes. The Assignment Status column shows if the settings according to the assigned templates are active green or if a further activation via Apply and Activate is required yellow. However, it is not possible to change template assignments for the managed object without discarding the managed object specific settings.
The Directory Browser allows to access the configuration in the Alerting Directory to check details of the currently active configuration. Step 7: Complete. The System Monitoring setup is completed for the managed systems in scope. In this step the status of all previous steps of the configuration is displayed. When configuring System Monitoring following the procedure described above, it is important to consider whether the assigned monitoring template is sufficient to reflect your monitoring requirement.
SAP has provided various monitoring templates over the past years to cover a wide range of products adopted by the most customers. These SAP provided monitoring templates is delivered within the component ST-CONT details see the section Content Update and contain the definitions of the metrics, events, and alerts as well as the details of settings such as the assigned threshold value, which can be found under Step 4 - Template Maintenance of the System Monitoring Guided Procedure.
The following example shows the view under Step 4 - Template Maintenance. There are multiple monitoring templates listed under the corresponding managed objects e. When double-clicking any of these templates, the detailed view is displayed at the right hand side. All the metrics, alerts and their setting details can be checked here. Nevertheless, it is easy to identify that the already activated metrics or alerts cannot be deactivated or the assigned threshold value cannot be modified anymore all settings are greyed out , which is made by design.
These predefined SAP delivered monitoring templates are called as the standard templates. Of course, standard templates alone could not fulfill the customer's monitoring requirement, considering the fact that each customer has own preferred set of metrics and also it can vary depending on the system role e. Therefore, we SAP come up with the concept custom monitoring template and each customer can flexibly define own preferred set of metrics in it. The custom template can be created conveniently by copying the standard template.
The user needs to first mark the corresponding standard template and press the button Create Custom Template.
0コメント