10 April 2025

Changes to the IBM Cloud Object Storage file naming convention for IBM Cloud Activity Tracker Event Routing

IBM Cloud Activity Tracker Event Routing will change the IBM Cloud Object Storage (COS) file naming convention for activity tracking events sent to COS buckets. With this change, customers that have a dependency on the current file naming convention might need to adjust automation to reflect the new naming convention. The format of the data in the files will not change.

The change will take effect on 15 May 2025. For more information, see Changes to Cloud Object Storage file naming convention.

7 March 2025

Removal of logdna targets

IBM Log Analysis and IBM Cloud Activity Tracker hosted event search will no longer be supported on 30 March 2025. IBM Cloud Activity Tracker Event Routing will stop supporting logdna targets at the same time and no events will be routed to these type of targets after that date. You should make sure that you have configured IBM Cloud Activity Tracker Event Routing to direct your activity tracking events to another destination before 30 March 2025. Any logdna targets still configured after 30 April 2025 will be removed automatically from your IBM Cloud Activity Tracker Event Routing configuration.

31 January 2025

Virtual private endpoints

IBM Cloud® Activity Tracker Event Routing now supports virtual private endpoints (VPE) for all API regions. For more information see, Using virtual private endpoints for VPC to privately connect to Activity Tracker Event Routing.

28 January 2025

Context-based restrictions

IBM Cloud® Activity Tracker Event Routing now supports context-based restrictions (CBR). For more information see, Restricting access by context-based restrictions.

07 January 2025

Some IBM Cloud® Object Storage events will be dropped.

IBM Cloud® Activity Tracker Event Routing will drop successful cloud-object-storage.object.read events that are initiated by IBM Cloud Logs instances because they are not needed.

23 September 2024

Additional service-to-service authentication support.

IBM Cloud® Activity Tracker Event Routing now supports service-to-service authentication to Event Streams endpoints.

09 September 2024

Changes to Management API IP addresses

The API Management IP addresses for the Dallas, Frankfurt, London, Sydney and Washington regions are changing on or after 14 October 2024. To avoid disruption, customers with firewalls must include the new IP addresses.

24 June 2024

Activity Tracker Event Routing support for IBM Cloud Logs targets.

Using the CLI, API, UI, or Terraform you can configure Activity Tracker Event Routing to send events to an IBM Cloud Logs instance. This adds to the existing support for IBM Cloud Object Storage, Activity Tracker hosted event search, and Event Streams targets.

For more information, see Configuring an IBM Cloud Logs target and Managing IBM Cloud Logs targets

20 June 2024

Configure IBM Cloud Activity Tracker Event Routing using the IBM Console

IBM Cloud Activity Tracker Event Routing provides a new user interface through the IBM Console where you can configure routes and targets. For more information, see Getting account settings using the UI.

15 April 2024

Chennai (in-che) region support

Chennai is now an online region for IBM Cloud Activity Tracker Event Routing. Services can now be provisioned Chennai and endpoints in Chennai can be used.

11 April 2024

Toronto (ca-tor) and Sao Paulo (br-sao) region support

Toronto and Sao Paulo are now online regions for IBM Cloud Activity Tracker Event Routing. Services can now be provisioned in those regions and endpoints in those regions can be used.

Increase routes and rules limits

The maximum number of routes for each account is increased to 30 and the maximum number of rules for each route is increased to 10.

03 April 2024

Osaka (jp-osa) and Tokyo (jp-tok) region support

Osaka and Tokyo are now online regions for IBM Cloud Activity Tracker Event Routing. Services can now be provisioned in those regions and endpoints in those regions can be used.

01 March 2024

Support for br-sao, ca-tor, jp-osa, jp-tok and in-che regions planned for April 2024

If you have services in the br-sao, ca-tor, jp-osa, jp-tok or in-che regions and you have an existing IBM Cloud Activity Tracker Event Routing configuration, action might be required to continue processing AT events in these regions. To determine if you are impacted, see Required actions for newly supported regions

26 September 2023

Madrid region support

Madrid is now an online region for IBM Cloud Activity Tracker Event Routing. Services can now be provisioned in Madrid and Madrid endpoints can be used. Platform metrics will continue flowing to the Frankfurt region.

17 July 2023

References to Activity Tracker Event Routing V1 API removed.

All references to the deprecated V1 API have been removed from the Activity Tracker Event Routing documentation.

18 November 2022

Activity Tracker Event Routing support for IBM® Event Streams for IBM Cloud® targets.

Using the CLI, API, or Terraform you can configure Activity Tracker Event Routing to send events to an Event Streams topic. This adds to the existing support for IBM Cloud Object Storage and Activity Tracker hosted event search targets.

New documentation locations for Activity Tracker Event Routing and Activity Tracker hosted event search

There are now two different locations for Activity Tracker documentation depending on your use case.

25 May 2022

New V2 API support for Activity Tracker Event Routing including the ability to configure service-to-service authorization for IBM Cloud Object Storage targets.

Highlights of this new support include:

• You are now able to route your global events to any Activity Tracker Event Routing hosted event search region even if Activity Tracker Event Routing is not present in the region.

• The Activity Tracker Event Routing configuration has been moved to be a global configuration so that all route definitions apply to all regions where the feature is present. This removes the requirement to configure Activity Tracker Event Routing in each region. Routing based on location is still possible.

• IBM Cloud Object Storage targets support service-to-service authorizations which eliminates the need to manage keys for your IBM Cloud Object Storage targets.

• The setting feature allows the account to choose the location where the Activity Tracker Event Routing metadata for their account is stored.

• The setting feature allows the account to choose one or more default targets for routing events. This removes the requirement to individually define routes in each region if you want to have all events from all regions to flow to a specific target.

• New /api/v2 APIs have been introduced to replace the existing V1 APIs.

• The V1 APIs are now deprecated and will be removed in a future release.

• For existing Activity Tracker Event Routing users, you will need to follow a migration process to use the new V2 features. For customers that have not yet configured a target using Activity Tracker Event Routing, you will default to V2 and will not require a migration.

Activity Tracker Event Routing available in Sydney (au-syd)

Activity Tracker Event Routing is now available in the in Sydney (au-syd) region. Learn more.

22 March 2022

Activity Tracker Event Routing available in Frankfurt (eu-de) and London (eu-gb)

Activity Tracker Event Routing is now available in the Frankfurt (eu-de) and London (eu-gb) regions. Learn more.

13 August 2021

General availability of Activity Tracker Event Routing

Learn more about Activity Tracker Event Routing.