---
name: metrics-router-about
title: About IBM Cloud Metrics Routing in IBM Cloud
description: IBM Cloud Metrics Routing is a platform service that you can use to configure the routing of platform metrics generated in your IBM Cloud account.
last-updated: 2024-10-09
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/metrics-router?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# About IBM Cloud Metrics Routing in IBM Cloud
{: #about}

IBM Cloud Metrics Routing is a platform service that you can use to configure the routing of platform metrics generated in your IBM Cloud account.
{: shortdesc}

You can use IBM Cloud Metrics Routing, a platform service, to manage metrics at the account-level by configuring targets and routes that define where data points are routed. IBM Cloud Metrics Routing can only route metrics that are generated in [supported regions](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-regions&format=markdown) by enabled services. Other regions, where IBM Cloud Metrics Routing is not available, continue to manage metrics by using [Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started&format=markdown). For more information about  IBM Cloud Metrics Routing, see [About IBM Cloud Metrics Routing](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-about&format=markdown).

IBM Cloud Metrics Routing is an IBM Cloud platform service that enables the routing of platform metrics to appropriate backend storage and analysis systems based on compliance needs.

Use IBM Cloud Metrics Routing to combine platform metrics from many regions into one monitoring instance or to segment platform metrics into multiple monitoring instances within a region as dictated by your operational requirements.
{: tip}

![A diagram that shows a sample IBM Cloud Metrics Routing architecture.](/images/metrics-routing-ov.png "IBM Cloud Metrics Routing architecture sample."){: caption="IBM Cloud Metrics Routing sample architecture" caption-side="bottom"}

## Configuring the account
{: #metrics-resources-config}

To configure IBM Cloud Metrics Routing in your account, you must define where metrics are routed and stored. You must configure 1 or more targets, and 1 or more routes. You must also configure the account settings.

- A target defines the resource and location where time series data is routed.  For more information, see [Targets](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-target&interface=api&format=markdown).

- A route defines the rules that indicate where time series data is routed in your account. For more information, see [Routes](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-routes&interface=api&format=markdown).

- The account settings configuration defines information such as default targets where metrics are collected in the account, type of endpoints that are allowed to manage the configuration, and allowed locations to store the data in the account. For more information, see [Account settings](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-settings&format=markdown).

You can configure the following types of targets:

| Target                                      | Type                     | When to use |
|---------------------------------------------|--------------------------|------------|
| IBM Cloud Monitoring         | `sysdig-monitor`         | Consolidate time series data to the region of your primary operations. |
{: caption="List of targets" caption-side="top"}


The following table outlines the locations where you can configure IBM Cloud Metrics Routing to collect and manage metrics:

| Geo                   | Region                   | IBM Cloud Metrics Routing |
|-----------------------|--------------------------|----------------------------------------------------|
| Asia Pacific        | Chennai (`in-che`)       | [No]{: tag-red} |
| Asia Pacific        | Tokyo (`jp-tok`)         | [Yes]{: tag-green} |
| Asia Pacific        | Sydney (`au-syd`)        |  [Yes]{: tag-green} |
| Asia Pacific        | Osaka (`jp-osa`)         | [Yes]{: tag-green} |
| Europe              | Frankfurt (`eu-de`)      | [Yes]{: tag-green} |
| Europe              | London (`eu-gb`)         | [Yes]{: tag-green} |
| North America       | Dallas (`us-south`)      | [Yes]{: tag-green} |
| North America       | Toronto (`ca-tor`)       | [Yes]{: tag-green} |
| North America       | Washington DC (`us-east`)   | [Yes]{: tag-green} |
| South America       | Sao Paulo (`br-sao`)     | [Yes]{: tag-green} |
{: caption="Supported locations" caption-side="bottom"}


## Features
{: #about-features}

- Consolidate time series data to the region of your primary operations

- Route time series data to one or multiple locations

- Improve your data residency compliance stature, keeping data at-rest within certain regions