Architecture decisions for service management
The following sections summarize the architecture decisions for service management for the deployment of Satellite on-premises or in hyperscaler pattern.
Architecture decisions for monitoring
| Architecture decision | Requirement | Option | Decision | Rationale |
|---|---|---|---|---|
| Monitoring | Monitoring of Satellite location and hosts |
|
IBM Cloud Satellite monitoring tool | By default, IBM Cloud Satellite automatically monitors and resolves certain alerts for the Satellite location setup and host infrastructure that can be accessed through IBM Cloud Satellite console and CLI. For more information, see Default monitoring for Satellite. |
| IBM Cloud® Monitoring | IBM Cloud Satellite can be integrated with a customer-owned IBM Cloud® Monitoring instance that is enabled for platform-level metrics to provide more detailed metrics. The monitoring instance can be configured to collect metrics for both the Satellite location and Satellite-enabled services that run in the Satellite location. | |||
| Monitoring Red Hat OpenShift clusters |
|
IBM Cloud® Monitoring | Manually deploy monitoring agents in Red Hat OpenShift clusters to forward metrics to a customer-owned IBM Cloud® Monitoring instance and get unified views of metrics for Red Hat OpenShift clusters and other cloud services that run at the Satellite location and within the Satellite managed-from region. For more information, see Setting up monitoring for clusters. |
Architecture decisions for logging
| Architecture decision | Requirement | Option | Decision | Rationale |
|---|---|---|---|---|
| Logging | Logging events from Satellite location and hosts |
|
IBM Cloud Satellite log analysis tool | By default, IBM Cloud Satellite automatically generates a set of logs for the Satellite location that can be accessed through the IBM Cloud Satellite built-in log analysis dashboard tools. For more information, see Analyzing Logs for Satellite Location. The log analysis instance can be configured to collect metrics for both the Satellite location and Satellite-enabled services that run in the Satellite location. |
| IBM Cloud Logs | IBM Cloud Satellite can be integrated with a customer provisioned [IBM Cloud Logs instance that is enabled for platform-level logs to get a comprehensive view and tools to manage logs for IBM Cloud Satellite and other IBM Cloud resources. | |||
| Logging events from Red Hat OpenShift clusters |
|
IBM Cloud Logs | Manually deploy logging agents in Red Hat OpenShift clusters to forward cluster logs to a customer-owned IBM Cloud Satellite and get a comprehensive view of logs for Red Hat OpenShift clusters and other cloud services that run at the Satellite location and within the Satellite managed-from region. For more information, see Setting up Logging for Clusters. |
Architecture decisions for auditing
| Architecture decision | Requirement | Option | Decision | Rationale |
|---|---|---|---|---|
| Auditing | Tracking and auditing Satellite location events | IBM Cloud Logs | IBM Cloud Logs | Customer-owned IBM Cloud Logs instance for IBM Cloud Satellite to forward audit events. IBM Cloud Logs tracks how users and applications interact with IBM Cloud Satellite. It can be used to investigate abnormal activity and critical actions and to comply with regulatory audit requirements. For more information, see Auditing events for Satellite. |
| Tracking and auditing Red Hat OpenShift clusters |
|
IBM Cloud Logs | Red Hat OpenShift on IBM Cloud automatically generates cluster management events and forwards these event logs to a customer-owned IBM Cloud Logs instance. For more information, see Events for Satellite clusters. |