Configuration scenarios for IBM Cloud Logs Routing (V3) in IBM Cloud
You can configure a centralized logging model, a geographic logging model or regional logging model when you setup IBM Cloud Logs Routing.
The following scenarios represent the most common logging configurations and will help you determine the appropriate setup for your v3 environment.
Scenario 1: How do I configure a centralized logging architecture in an IBM Cloud Account
In a centralized logging configuration, all platform logs for your entire account are consolidated into a single IBM Cloud Logs instance.
This approach simplifies log management by providing a unified view of all platform activities across your account.
To implement this scenario in v3, you will need to create one target pointing to your centralized IBM Cloud Logs instance and configure one route with a wildcard rule to capture all platform logs regardless of their source region.
Scenario 2: How do I configure a regional centralized logging architecture in an IBM Cloud account
The geographic logging scenario is designed for organizations that maintain multiple logging instances distributed across different geographic locations.
In this configuration, platform logs from various regions are routed to their nearest or designated regional IBM Cloud Logs instance based on geographic proximity or data residency requirements. This approach balances centralized visibility with geographic distribution, allowing you to route logs from multiple regions to a smaller number of strategically located IBM Cloud Logs instances.
To implement this scenario, you will need to create multiple targets (one for each geographic IBM Cloud Logs instance) and configure routes with appropriate region-based filters to direct logs to the correct geographic destination.
Scenario 3: How do I configure a distributed or regional logging architecture in an IBM Cloud account
Regional logging represents the most distributed approach, where each IBM Cloud region has its own dedicated IBM Cloud Logs instance.
This configuration ensures complete regional isolation of log data and is often used to meet strict data residency or compliance requirements. In this scenario, platform logs generated in a specific region are routed exclusively to the IBM Cloud Logs instance deployed in that same region.
To implement this scenario in v3, you will need to create a separate target and route for each region where you operate, ensuring that each regional route includes filters that restrict log routing to only that region's IBM Cloud Logs instance.