Best practices for monitoring Cloud Pak for Data
It is critical to monitor the health of your IBM Cloud Pak® for Data environment on a regular basis. By monitoring your Cloud Pak for Data deployments and the clusters where your deployments are running, you can ensure that the environment is performant and is scaled to support your business needs. In addition, routine monitoring can help prevent unexpected outages and instability.
Recommended tasks
Task | Purpose | Frequency |
---|---|---|
Performing routine IBM Cloud Pak for Data monitoring | Regularly monitor your Cloud Pak for Data deployments to ensure that they are running as expected. As part of your Cloud Pak for Data monitoring routine, review alerts to help you address any potential problems. |
It is recommended that you perform this task at least once per day or once per shift. However, if there is a large variation in the number of concurrent users or jobs, it is recommended that you perform this task more frequently during peak activity. |
Setting up quotas and alerts | Quotas provide a way for you to specify the maximum amount of memory and vCPU you want the platform, a specific service, or a project to use. Enable quotas to help detect problems before they occur. |
You should set up quotas and alerts after you install Cloud Pak for Data. In addition, it is recommended that you review these settings every few weeks to determine whether you need to adjust the settings based on your actual use. |
Performing routine cluster monitoring | Regularly monitor the Red Hat OpenShift Container Platform cluster to maintain the health of your Cloud Pak for Data deployments. |
It is recommended that you perform this task at least once per day or once per shift. However, if there is a large variation in the number of concurrent users or jobs, it is recommended that you perform this task more frequently during peak activity. |
Integrating with Prometheus | Run Prometheus queries to monitor Cloud Pak for Data deployments on Red Hat OpenShift Container Platform. |
|