Planning the account configuration

Locations and services

Check the regions where you operate and identify how you can manage those metrics in the account:

• Identify the locations where you can configure IBM Cloud Activity Tracker to manage metrics. Check Locations.
• Identify which services in those locations generate metrics that you can route through IBM Cloud Metrics Routing. Check Services generating metrics.

You can use IBM Cloud Metrics Routing to manage metrics at the account-level. IBM Cloud Metrics Routing can only route metrics that are generated in supported regions. Other regions, where IBM Cloud Metrics Routing is not available, continue to manage metrics by using IBM Cloud Monitoring.

Metadata location

Decide the location in your IBM Cloud account where the IBM Cloud Metrics Routing account configuration metadata is stored.

You can choose any of the supported locations where IBM Cloud Metrics Routing is available. For more information, see Locations.

Take into account any corporate or industry compliance requirements such as Financial Services Validated locations, or EU-managed regions.

You can define a primary metadata location and a backup metadata location. Once a primary location is set, you can change it to a different region but you cannot disable it.

You must define a primary metadata location in the account before you can configure destinations and rules to route metrics in the account.

Endpoints allowed

You can use public endpoints, private endpoints or both to manage the IBM Cloud Metrics Routing account configuration.

Decide whether public endpoints, private endpoints, or both are allowed to manage the IBM Cloud Metrics Routing account configuration. For more information, see Enforcing private endpoints to configure IBM Cloud Metrics Routing resources.

Configure private endpoints and disable public endpoints when you require to be Financial Services Validated.

Target locations

Define the locations where an account administrator can configure targets to collect metrics. You can choose any of the supported locations where IBM Cloud Metrics Routing is available. For more information, see Locations.

To enforce target locations in the account, you can configure the account settings and specify the locations that are allowed.

Take into account any corporate or industry compliance requirements such as Financial Services Validated locations, or EU-managed regions.

The location of a target definition must be a supported location where IBM Cloud Metrics Routing is available. The target can configure a resource in the same account where the metrics are located or in a different account. In addition, the resource can be located in any region where that type of resource is supported in IBM Cloud.

For each target that you define in the same account where metrics are generated, you must define a service to service authorization between the IBM Cloud Metrics Routing service and the IBM Cloud Monitoring instance that you configured as your destination in the target. For more information, see Managing authorizations to grant access between services.

For each target that you define in a different account from the one where metrics are generated, you must define a service to service authorization in the account where the target resource is available between the IBM Cloud Metrics Routing service and the IBM Cloud Monitoring instance that you configured as your destination in the target. For more information, see Managing authorizations to grant access between services.

Default targets

You can define up to 2 default targets in the account.

• Each target collects metrics that are not explicitly managed in the account's routing rules.
• Each target must be defined in the account before you can configure it as default one in the account.
• If you define more than 1 default target, all default targets get a copy of the metrics that does not have a clearly defined routing rule to indicate where to route them in the account.

Define 1 default target per account to configure where metrics that are not explicitly managed in the account's routing rules are routed. Consider defining a second default target per account when you want to collect the data in a backup location or account.

Number and location of targets

Define the targets where you plan to collect metrics based on your regulatory and corporate requirements.

• You can have 1 target per region to collect metrics for that region. Use this option to reduce latency and network connectivity issues.

• You can have 1 target to collect metrics across the entire account.

• You can define targets within the account or in a different account.

For more information, see Targets.

Routing rules in the account

Define the routing rules that indicate how to route metrics in your account.

• Routes are global.

• You can define up to 30 routes per account.

• You can define 1 or more routes to configure how metrics across all regions in your account are collected and stored in 1 or more targets.

• For each route that you define, you can configure up to 10 rules. These rules are applied in order. When a rule is identified for a region, any follow up rules withing that route definition that apply to that region are not considered.

Decide if you want to drop the collection of metrics in 1 or more regions. Check any compliance requirements to confirm that you can.

-To drop the collection of metrics in 1 or more regions, you can configure a route for those regions with no targets defined.

For more information, see Routes.