---
sourceDocument: Brazil Telecommunications Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-service-ops

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Metric aggregation modes

# Metric aggregation modes {#ariaid-title1}

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Metric aggregation rolls up raw metrics collected from individual network resources into calculated metrics on parent or anchor configuration items (CIs). The aggregation mode determines how source resources are selected and
where the aggregated result is published.
By default, a pull connector collects raw metrics and publishes one value per network resource, such as a single metric value for each mobile cell. There is no built-in way to combine those per-resource values into a
higher-level metric.

Metric aggregation addresses this gap. It reads the raw metric values for a set of related resources and applies an aggregate function such as average, maximum, or minimum. It then publishes a calculated metric so that the result can be viewed at a higher level of the network. An aggregation runs as a scheduled job that calls the metric aggregation scripted extension point.

## Key benefits {#metric-aggregation-modes__section_benefits}

Metric aggregation provides the following benefits:

* View metrics at higher levels of the network, according to Baseband Unit (BBU) or per Network Site, instead of only per cell.
* Aggregate metrics across a defined range of resources, such as a range of SIM cards.
* Define new aggregations without changing product code by configuring scheduled jobs that call a scripted extension point.

## How it works {#metric-aggregation-modes__section_how_it_works}

Each aggregation runs in one of two modes. The mode determines how source resources are selected and where the calculated metric is published.

Hierarchy mode
:   The aggregation traverses configuration management database (CMDB) relationships downward from each target CI to collect the matching source CIs, then writes one calculated metric onto each target CI. Use hierarchy
    mode to roll per-cell metrics up to each parent resource, according to BBU or per Network Site.

Flat mode
:   The aggregation selects source CIs directly, optionally filtered by a name range or by field values, and writes a single calculated metric onto one anchor CI. Use flat mode for range-based or fleet-wide metrics where
    no single parent CI exists to hold the result.

A range identifies a contiguous set of resources by name, such as a range of SIM cards. You can also apply field filters so that only resources meeting a condition are included in the aggregation. For example, you can filter to include only resources whose operational status indicates that they are active.

An aggregation runs one of the following functions, set through the `aggregate` parameter: average (`avg`), sum (`sum`), maximum (`max`), minimum (`min`), count (`count`), and the 95th percentile (`p95`).

After an aggregation run produces a calculated metric, the metric base framework raises an event to bind the metric to a CI. After the metric-to-CI binding completes, the calculated metric is stored in the metric base
(Clotho) against the bound CI and becomes available to view.

## Considerations {#metric-aggregation-modes__section_considerations}

Consider the following when you plan an aggregation:

* In hierarchy mode, a depth limit bounds how far the traversal descends through the CMDB. The depth limit helps prevent the traversal from following relationships beyond the resources you intend to aggregate.
* In flat mode, the calculated metric is not tied to an existing parent CI, so you specify an anchor CI to hold the result.
* An aggregation runs on the schedule defined for its scheduled job. Calculated metrics appear after the next successful run and metric-to-CI binding.
**Related concepts**   

* [Metric aggregation scripted extension](https://www.servicenow.com/docs/nKBY7x8VPAoMAPOnIaxK7Q "You can define custom KPI calculations on top of raw metrics collected from source systems. Configurable formulas combine, aggregate, and label metrics without requiring code changes to the platform.")
* [Metric-to-CI binding](https://www.servicenow.com/docs/b1NLp~k1I6Y~3UnBeDK6~g "Metric-to-CI binding associates metrics collected by a pull connector with configuration items (CIs) in the Configuration Management Database (CMDB). Default binding logic is used for each supported connector, which you can override with a custom implementation.")
* [MPN data model](https://www.servicenow.com/docs/a_KJsS_1NPUls6rwrgoliA "The Mobile Private Network (MPN) data model extends the Telecom data model to represent the physical hardware and virtual network functions that make up a mobile private network. It also represents the relationships that connect them.")  
**Related tasks**   

* [Configure a metric aggregation job](https://www.servicenow.com/docs/WMzpe4k1_hM~rdyt6dVlCg "Configure a scheduled job to aggregate raw metrics into a calculated metric on a parent or anchor configuration item (CI). Aggregated metrics let you view performance data at a higher level of the network.")
* [Create a custom metric aggregation implementation](https://www.servicenow.com/docs/tTZBr2E6hQYxuBMJkqj1HA "Create a custom implementation of the metric aggregation scripted extension point when the default aggregation modes don't cover a calculation you need.")  
**Related reference**   

* [Metric aggregation configuration reference](https://www.servicenow.com/docs/GsflslmFF_ggscCXPCxb0g "The configuration object passed to the metric aggregation scripted extension point defines what to aggregate, how to aggregate it, and where to publish the result. The parameters that apply depend on the aggregation mode.")