Observability support for Montreal before the observability services are available in Montreal

Until the IBM Cloud Logs Routing service is available in Montreal, platform logs are delivered to the IBM Cloud Logs instance configured for the Washington DC (us-east) region. Logs sent from Montreal include a logSourceCRN field such as ca-mon, mon01, mon02, or mon03. If an IBM Cloud Logs Routing tenant is not configured in us-east, then you need to create a tenant in us-east to receive platform logs for the Montreal region.

Activity tracking events from Montreal can be configured in IBM Cloud Activity Tracker Event Routing to be sent to any region.

If you have an IBM Cloud Activity Tracker Event Routing route defined that contains a wildcard rule, then your Montreal events will be found in the target associated with the route. If you have a default target specified in the IBM Cloud Activity Tracker Event Routing settings, then your Montreal data will be located in that default target unless another routing rule directs the events to another target destination. A rule of some type must be configured to route us-east data to handle events sent by Montreal.

Platform metrics from Montreal can be configured in IBM Cloud Metrics Routing to be sent to any region.

If you have an IBM Cloud Metrics Routing route defined that contains a wildcard rule, then your Montreal metrics will be found in the target associated with the route. You can also define a route rule with a ca-mon location inclusion filter. If you have a default target specified in the IBM Cloud Metrics Routing settings, then your Montreal data will be located in that default target unless you have a route that overrides it.

If platform metrics are configured to route your Montreal platform metrics by a us-east IBM Cloud Monitoring instance, create an IBM Cloud Monitoring support ticket with title "Enable Monitoring Provisioning in Montreal" before 14 July 2025 22:00 UTC to enable the provisioning of an IBM Cloud Monitoring instance in ca-mon . After you provision your IBM Cloud Monitoring instance in ca-mon, configure platform metrics with your new IBM Cloud Monitoring ca-mon instance to avoid the loss of Montreal metrics.

You need to have one or more IBM Cloud Logs instances to work with platform logs and activity tracking events from Montreal. You also need an IBM Cloud Monitoring instance in the region where you route platform metrics.

Actions after observability services are available in Montreal

After IBM Cloud observability services are available in Montreal, you can reconfigure your routing to send to IBM Cloud Logs and IBM Cloud Monitoring instances in Montreal. You need to configure Logs Routing for the Montreal region to continue receiving platform logs for the region.