Monitoring configuration

Monitoring is installed in the management-monitoring namespace.

Note: If you must uninstall and reinstall Monitoring for some reason, if you are using local storage, you must delete all data from the created folders/volumes manually. For dynamically provisioned storage, no action is required. The data is automatically deleted.

ibm-management-monitoring

The following procedure describes how to customize the configuration parameters for Monitoring using the installation YAML. Customize your out of the box Monitoring installation using the installation YAML. For more information, see the Monitoring parameters table.

Important: The following important settings for Monitoring cannot be customized using the installation YAML, and these must be customized separately:

• Data retention and metric summarization parameters are not configured as part of the Monitoring operator, they are not customized using the installation YAML. They must be configured in the observability service in Red Hat Advanced Cluster Management, for more information, see the Enabling the observability service in Red Hat Advanced Cluster Management topic.

• The Monitoring DataProvider Management configuration parameters are not included in the installation YAML. See Installing and uninstalling IBM Monitoring DataProvider Management for more information about these parameters.

Note: If at any time, before or after monitoring configuration, you access Monitoring menus from the console and a 401 self-signed error message is returned, refer to 401 self-signed certificate error returned when accessing Monitoring menus to troubleshoot.

To update the configuration parameters using the installation YAML after you install Monitoring, complete the following steps:

1. Run the following command to edit the Installation custom resource:

   oc edit installations.orchestrator.management.ibm.com <installation_name> -n <IBM Cloud Pak for Multicloud Management_namespace> -o yaml
   

   Where <installation_name> is the name for your installation instance, for example, cp4mcm-install. <IBM Cloud Pak® for Multicloud Management_namespace> is your IBM Cloud Pak for Multicloud Management namespace, for example, cp4mcm.

2. Add or update the parameters for the specific feature or function that you are configuring in the monitoringDeploy section. Refer to the Monitoring parameters and the following example yaml snippet for help updating these parameters.

   monitoringDeploy:
     global:
       monitoring:
         analytics: true
         ha: false
       metric:
         summary
           enabled: false
       environmentSize: size0
       minReplicasHPAs: 1
       agentmgmt:
         provider:
           autoRemove: true
           ttl: 24
       persistence:
         storageClassOption:
           cassandrabak: none
           cassandradata: icam-local-storage-cassandra
           couchdbdata: icam-local-storage-couchdb
           datalayerjobs: icam-local-storage-datalayer
           elasticdata: icam-local-storage-elasticsearch
           kafkadata: icam-local-storage-kafka
           zookeeperdata: icam-local-storage-zookeeper
         storageSize:
           cassandrabak: 50Gi
           cassandradata: 50Gi
           couchdbdata: 5Gi
           datalayerjobs: 5Gi
           elasticdata: 5Gi
           kafkadata: 25Gi
           zookeeperdata: 1Gi
     autoconfig:
       testActive: "true"
       testInterval: "5"
       disableAlerts: "true"
       useAllLocations: "false"
   

3. Wait until the CR status is success. It might take a substantial amount of time. You can run the following command to check MonitoringDeploy CR status:

   oc get monitoringdeploy $(oc get monitoringdeploy -n management-monitoring --no-headers | awk '{print $1}') -n management-monitoring -o yaml
   

Monitoring parameters