| copyright | lastupdated | subcollection | keywords | ||
|---|---|---|---|---|---|
|
2023-12-18 |
pattern-oracle-disaster-recovery-on-powervs |
{{site.data.keyword.attribute-definition-list}}
{: #architecture-service-management}
The following sections summarize the architecture decisions for service management for the Oracle Disaster Recovery on IBM Power Virtual Servers pattern.
| Architecture decision | Requirements | Decision | Rationale |
|---|---|---|---|
| Monitoring (Application) | Provide Integration, Exception, Health, and System Monitoring | Bring your own tools (BYOT) for Oracle DB like Oracle Enterprise Manager | Displays the status of managed objects and detailed drill down to each single metric or event. Shows the history of each metric in the Metric Monitor Automatic alert generation when thresholds are violated |
| Monitoring Cloud (Platform) | Monitor and correlate performance metrics and events | For PowerVS use “nmon” | Automates root-cause analysis by using event correlation, performance thresholds, errors, changes, and analysis of service level agreement (SLA) violations Provides full context across the application infrastructure supporting all physical, virtual, and serverless services and functions Provides data and actionable insights to monitor the applications, understand and respond to system-wide performance changes, optimize resource utilization, and get a unified view of operational health |
| Logging | Diagnose issues, analyze stack traces and exceptions, identify the source of errors, and monitor different log sources through a single view | Oracle DB Log Analysis Tools | Bring your own tools for Oracle |
| Alerting | Provide tracking and alerting functions across application and infrastructure. | IBM Cloud Logs and IBM Cloud Monitoring | Provides infrastructure monitoring, logging, alerting, and tracking/auditing functions across VPC and Power System Virtual Server environment |
| {: caption="Architecture decisions for servcie management" caption-side="bottom"} |