IBM Cloud Docs
Managing metrics in a new location after Monitoring is available

Managing metrics in a new location after Monitoring is available

To manage metrics from IBM Cloud services that generate metrics in a new region where the IBM Cloud Monitoring service is not available until a later date, complete these instructions.

For example, the Madrid region opened for business in June 2023. IBM Cloud services that are available and generate metrics send currently those metrics to the Frankfurt region. You can manage metrics from these services in Frankfurt. Platform metrics include the attribute ibm_location that specifies the region, location, or data center where the resource is available. For example, for Madrid, you can see the location of metrics set to eu-es.

You cannot control when an IBM Cloud service makes the switch to send metrics from one region to another one. However, you can provision an instance in the new region to prepare for that switch.

Data is not sent to both locations, complete the steps before that switch is done by a service to mitigate any loss of data.

Flow of metrics in a single region
Figure 1. Flow of metrics in a single region

Complete the following steps to enable the service in the new region:

Step 1. Provision an instance of the service in the new region

As soon as the IBM Cloud Monitoring service is available in the new region, for example, Madrid, complete the following steps:

  1. Create a new IBM Cloud Monitoring instance.

  2. Configure IAM access for the new instance.

Step 2. Configure the new instance

Complete the following steps:

  1. Configure platform metrics.

    • The Schematics service will continue to send metrics to the Frankfurt region.

    • For Cloud Object Storage buckets, once the service makes the change to send metrics to Madrid, you will continue to receive metrics in Frankfurt. To move the metrics that are gerenared by a bucket to be managed through Madrid, you must use the COS Resource Configuration API to reconfigure the Monitoring instance to the one located in Madrid. Otherwise, these metrics will continue to go to the instance that is configured for the bucket.

  2. Customize the UI for the new instance as needed. Add your custom dashboards.

    For example, you might need to update the location to eu-es for a configuration in the Madrid location.

  3. Create any alerts that are required for your organization on the new instance.

Step 3. [Optional] Configure monitoring agents

If you have monitoring agents configured to send data from Kubernetes clusters or Openshift clusters, for example, you can update the agents to point to the new instance in the new location (for example, Madrid).

For more information, see:

Step 4. Check the new instance is working

To monitor metrics, launch the web UI, and verify platform metrics are flowing to your instance. For more information, see Working with platform metrics.