Monitoring activity tracking events in IBM Cloud Logs
You can use the IBM Cloud Logs service to monitor and alert on activity tracking events that are generated in an IBM Cloud account.
The following diagram shows the high level view when the destination is an IBM Cloud Logs instance:
Before you can monitor activity tracking events that are generated in an IBM Cloud account, you must configure the IBM Cloud Activity Tracker Event Routing service in the account to define what activity tracking events you want to collect, the destination where you want to monitor the events, and the routing rules that define where the events are routed.
- You can configure 1 or more IBM Cloud Logs instances in the account.
- The IBM Cloud Logs instances can be located in the same account where events are generated or in a different account.
- You must define a service to service authorization between IBM Cloud Activity Tracker Event Routing and IBM Cloud Logs to grant permissions to the IBM Cloud Activity Tracker Event Routing service to send events to the IBM Cloud Logs service.
For more information, see:
- Getting started with IBM Cloud Activity Tracker Event Routing
- IBM Cloud services that generate events that are managed through IBM Cloud Activity Tracker Event Routing
Central model
Configure IBM Cloud Activity Tracker Event Routing in your account to route activity tracking events to 1 IBM Cloud Logs instance if you have a requirement to centralize activity tracking events.
The following image shows a high-level view of the account when you adopt a central model:
Data locality model
Configure IBM Cloud Activity Tracker Event Routing in your account to route activity tracking events to multiple IBM Cloud Logs instances if you have a requirement to maintain data locality.
The following image shows a high-level view of the account when you adopt a data locality model:
