Technical Monitoring and Alerting infrastructure helps you to improve the performance and health of systems in complex, heterogeneous landscapes. The following table shows the comparison of the Technical Monitoring and Alerting infrastructure with the traditional CCMS-based monitoring infrastructure:
Operation | Central CCMS | Technical Monitoring and Alerting |
---|---|---|
Configuration | Configuration has to be performed on central and managed systems. | Configuration has to be performed only on the central (SAP Solution Manager) system. It gets automatically distributed to managed systems. |
Agent infrastructure | CCMS agents have to be updated and configured manually. | Diagnostic agents are automatically updated and configured. |
Landscape awareness | Landscape setup and changes have to be adjusted manually. | Landscape setup and changes are automatically detected and updated. |
Mass maintenance | Configuration has to be done per managed system. | Configuration can be done on multiple managed systems at the same time using template concept. |
Central administration | Not applicable | Operation tasks can be performed from the Solution Manager Administration Work Center, centrally. |
Self monitoring | Not applicable | Self monitoring is available for SAP Solution Manager landscape and infrastructure components. |
Alert flooding | Not applicable | Prevents alert flooding by grouping metrics and alerts |
Graphical overview | Not applicable | Provides graphical overview of landscape status |
Technical Monitoring depends on:
Technical Administration, for details of work modes, to minimize redundant alerts
Technical Administration, for details of system users, external users, and business partners, to send notifications
IT Service Management to create support messages