About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Required actions for newly supported regions
If IBM Cloud® Activity Tracker Event Routing is planned to be supported in a currently non-supported region, all existing customers will need to evaluate their IBM Cloud Activity Tracker Event Routing configurations and make any required changes. IBM will announce if a new region is supported.
Check whether you have the correct permissions
Log in to the IBM Cloud by using an ID with Cloud Identity and Access Management with Administrator permissions.
Check whether the routing rules capture events for the new regions
With routing rules, you can change the destination (the target) where AT events flow based on the region of the AT events. This routing includes global events.
The routing rules determine which events are matched for routing.
Run the command ibmcloud at route ls
.
This example shows a route where events from all locations (all regions and global events) are routed to a target.
$ ibmcloud at route ls
OK
Name ID Rules Route Version API version CreatedAt UpdatedAt
es_demo_route 021ab990-6799-4a99-bb9b-99b4fe26abfc [[aa345799-99c2-9982-99a8-1e9954926295],[*]] 0 2 2023-11-28T17:00:30.701Z 2023-11-28T17:00:30.701Z
If you have a configuration similar to this example, where there is a wildcard (*
) location that is defined in the routing rule, then all of your events will be routed to that target when the new IBM Cloud Activity Tracker Event
Routing regions are enabled.
This example shows a route where only the global events are routed to a target. All of the regional events are not processed and are discarded.
$ ibmcloud at route ls
OK
Name ID Rules Route Version API version CreatedAt UpdatedAt
global-to-cos 08199417-9ec7-4d99-b9b4-41cd2b1b99a1 [[cded994e-a999-9cc9-b499-24099955d286],[global]] 0 2 2023-05-26T12:52:53.536Z 2023-05-26T12:52:53.536Z
If you have a configuration similar to this example, and only a subset of regions (or global) are listed, then you need to either add the newly supported regions to your configuration, or change the location to use the wildcard (*
)
location.
For more information about configuring routes, see Managing routes.
Check whether a default target is configured in your account
If you do not have a route that is configured, check if you have a default target that is configured in your account.
The default target in the IBM Cloud Activity Tracker Event Routing settings is the destination where activity tracker (AT) events are sent if there are no routing rules that match an event’s region.
Run the command ibmcloud at setting get
.
The “Default targets” array shows up to 2 defined targets that receive AT events, if there is no match in the routing definition.
For example, this shows that there are no default targets configured.
$ ibmcloud at setting get
OK
IBM Cloud Activity Tracker Event Routing settings
Metadata region primary: us-south
Metadata region backup: us-east
Default targets: [ ]
This example shows that a default target is configured.
$ ibmcloud at setting get
OK
IBM Cloud Activity Tracker Event Routing settings
Metadata region primary: us-south
Metadata region backup: us-east
Default targets: [“aa345994-79c2-4592-99a8-1e1994926295”]
For more information about defining targets, see Managing targets.
If you have a default target defined, then events not matching your account’s routing rules will be routed to the default targets and you are not affected by this change.
If you do not have a default target defined, then continue to the next step.
Define a default target
Unless you are specifically trying to drop AT events, using the default target is the best way to ensure that all data is retained somewhere. You can configure a default target with a command similar to ibmcloud at setting update --default-target <target-id>
.
For example:
$ ibmcloud at setting update --default-targets aa34579944-99c2-4592-99a8-1e1994926295
Are you sure you want to update the IBM Cloud Activity Tracker Event Routing settings for your account? [y/N]> y
OK
IBM Cloud Activity Tracker Event Routing settings
Metadata region primary: us-south
Metadata region backup: us-east
Default targets: [aa34579944-99c2-4592-99a8-1e1994926295]