Model Mapping
Through the powerful data processing workflow of the ONE platform, data is transformed into the standard data model of ONE.
Model Mapping Components
The ONE platform provides Metric Mapping, Log Mapping, Call Chain Mapping, and Event Mapping components. By specifying field matching, data is converted into the protocol fields of the ONE platform. For more information on the model definitions of the ONE platform, refer to the Model Definition section.
Getting Started
Metric Mapping V2 (Recommended)
When you need to integrate external data into ONE, use Metric Mapping V2 to organize metric names, values, timestamps, types, dimensions, and tags so that the processed data meets metric ingestion requirements.
When creating a metric mapping, use Metric Mapping V2 whenever possible. This component consolidates metric fields, dimensions, and tags and lets you preview mapping results before publishing.
Choose a metric integration mode
Choose an integration mode based on whether the metric already exists in ONE. This prevents duplicate metric creation and incorrect associations with existing metrics.
| Integration mode | When to use |
|---|---|
| Dynamic Metric Registration | Register metrics from collected data. If CMDB Extraction is configured on the current branch, the corresponding instances are automatically associated with the metrics. |
| Mapping System Metrics | Associate collected metrics with existing metrics in ONE. |

Configure dynamic metric registration
Select Dynamic Metric Registration when metric names and values need to be read directly from collected data. Then select the metric name format that matches the source data structure.
The Metric Name Format supports the following options:
| Format | Configuration |
|---|---|
| Metric name and metric value are in separate fields | Select the source fields that store the metric name and metric value. |
| K:V pairs describe metric names and values | Select one source field that stores K:V pairs. After you select this format, the separate Metric Value field is hidden. |
Configure the remaining basic metric fields:
| Field | Required | Description |
|---|---|---|
| Metric Name | Yes | Select the field that stores the metric name. When using the K:V format, select the field containing the metric names here. |
| Metric Value | Yes | Select the field that stores the metric value. You do not need to select this field separately when using the K:V format. |
| Metric Value Timestamp | Yes | Select the field that stores the time when the metric value occurred. Only millisecond timestamps are supported. |
| Reporting Unit | No | Select the field that stores the unit. If the source data includes a metric unit field, map it to a unit supported by ONE. |
| Metric Type | Yes | Map the type in the source data to a metric type supported by ONE. |
The Metric Type must map to a metric type supported by ONE. If the type is not mapped correctly, the data cannot be ingested.

Map source metrics to system metrics
When a metric already exists in ONE, select Mapping System Metrics to associate each source metric with a system metric.
- Select the source fields for Metric Name, Metric Value, and Metric Value Timestamp.
- Click Add Mapping. A new metric mapping row appears.
- Enter the source metric name in Metric Name in Data.
- Select the metric to associate in Metric Name in System.
- After selecting the system metric, click Dimension Mapping if you need to add dimensions.
- Repeat these steps to add other metrics.
When selecting a system metric, search by metric name, metric ID, metric category, or tag. You can also select a metric category on the left and then choose a metric from the results on the right.
The page also provides Import Metrics, Export Metrics, Import Dimensions, Export Dimensions, and Create Metric operations.

Add metric dimensions
After configuring the metric fields, add entity dimensions and independent dimensions to analyze metric data from different perspectives.
Entity dimensions come from associated entity instances. Instances registered by the CMDB Extraction or CMDB Dynamic Registration components can serve as entity dimensions for metrics.
Configure fields that are not directly related to an entity but are required for metric analysis as independent dimensions:
- Click Add Dimension. A new dimension configuration row appears.
- Select Field in Data.
- Enter or confirm the Dimension ID.
- Under Dimension Configuration, select Dimension or Batch Dimension.
- Enter the Dimension Name.
- If a source field value needs to be converted, use Enumeration Mapping in the same row.
The page provides the dataCenterId dimension by default. If you do not select a source field for it, the system uses the data center associated with the current task.
Add metric tags
After configuring dimensions, add tags to support subsequent metric queries and distinguish metric data.
The system reads tags from associated entity instances and adds them to the metric data. To add independent tags:
- Click Add Tag to open the source field selection dialog.
- Search for and select a source field.
- Click OK. A new tag configuration row appears.
- Enter the Tag Key in the new row.
- If the tag is no longer required, delete it from the Operation column.
In Mapping System Metrics mode, independent tags do not apply to preset metrics.
Metric Mapping
The Metric Mapping component offers three mapping schemes to map basic information, dimensions, and tags of metrics.
-
Integrated Metric Extension: Quickly integrate external metrics into the ONE platform for data analysis. Metrics integrated this way can be viewed in the Dashboard and Data Exploration modules.

-
Dynamic Metric Registration (Associated with CMDB): Quickly integrate external metrics into the ONE platform and associate CMDB instances extracted from the preceding process with the entity dimensions of the metrics. This allows for more analytical dimensions based on entities. Metrics integrated this way can be viewed in the Dashboard and Data Exploration modules.

-
Mapping System Metrics (Associated with CMDB): Match external metrics one-to-one with the standard metrics in the ONE platform's system. These system metrics, refined through industry practice, are deeply used in multiple modules of the product.

Log Mapping
The Log Mapping component allows configuration of basic information and attribute mapping for logs.

Event Mapping
The Event Mapping component transforms external events and alert data into the standard event model of the ONE platform. It supports configuring basic information such as event type, level, status, occurrence and end times, and raw event information. It also allows setting tags and attributes for events to enhance the platform's analytical capabilities.

Alert Mapping
When Prometheus, Zabbix, a cloud platform, or another third-party system reports alerts, use Alert Mapping to normalize the alert status, level, data source, resource domain, and labels so that the data conforms to the ONE alert model.
Configure basic alert fields
First, map fields in the source data to ONE alert attributes to ensure that each alert contains basic information such as its name, status, level, and source.
| Field | Required | Description |
|---|---|---|
| Alert Status | Yes | Select the source field that stores the alert status, and use Enumeration Mapping to normalize its values. |
| Alert Name | Yes | Select the source field that stores the alert name. |
| Alert Level | Yes | Select the source field that stores the alert level, and use Enumeration Mapping to normalize its values. |
| Alert Data Source | Yes | Select the source field that identifies the system from which the alert originates, and use Enumeration Mapping to normalize the source name. |
| Resource Domain | Yes | Select the resource domain field in the source data, and map its values to resource domains that already exist in the current ONE environment. |
| Uniqueness Constraint | Yes | Select one or more fields as the basis for identifying alert uniqueness. You can select up to five fields. |

Normalize alert enumeration values
Source systems may use different values for statuses, levels, and data sources. Use Enumeration Mapping to convert these values to the values used by ONE.
- Select the corresponding source field.
- Click Enumeration Mapping to the right of the field.
- Enter the corresponding source data value for each ONE enumeration value.
- If multiple source values represent the same result, separate them with semicolons as indicated in the input field.
- Click Save to complete the mapping.
The Enumeration Mapping button is unavailable until you select a source field.
Map alert status
Alert status supports the following target values:
| Target status | Description |
|---|---|
| Alerting | Indicates that the alert is still ongoing. |
| Recovered | Indicates that the alert has recovered. |
| Closed | Indicates that the alert has been closed. |
When configuring status enumeration mappings, associate the corresponding time fields as prompted on the page:
- Alerting: You can associate the alert occurrence time and alert update time.
- Recovered: Associate the alert recovery time.
- Closed: Associate the alert close time.
- Time fields marked with
*are required.

Map alert levels
ONE provides the following alert levels:
| Alert level |
|---|
| Reminder |
| General |
| Warning |
| Severe |
| Fatal |
For example, map warning, WARN, or other synonymous values from the source system to the corresponding level based on their actual meaning.
Map alert data sources
ONE supports mapping source values to the following types:
- Prometheus
- Zabbix
- Alibaba Cloud
- Huawei Cloud
- China Telecom Cloud
- Tencent Cloud
- Third Party
If the actual source does not belong to a specific platform listed on the page, map it to Third Party as appropriate for your business scenario.
Map resource domains
The resource domain enumeration list comes from the current ONE environment. After you enter source resource domain values for the corresponding resource domains, alert data uses the mapped resource domains.
Resource domains may differ between environments. Refer to the resource domains displayed in the Enumeration Mapping window in the current environment.
Associate alert entities
After configuring the basic fields, confirm that the alert contains entity association information so that you can locate the corresponding resource from the alert later.
The Alert Mapping component automatically associates entities based on the _CMDB field in the data. You do not need to select an entity again in this component.
To associate an alert with an entity, generate a valid _CMDB field in an earlier step of the processing flow.
Set a uniqueness constraint
A uniqueness constraint provides the basis for determining whether an alert is unique.
- In Uniqueness Constraint, select a field from the data.
- Confirm that the field can distinguish different alerts.
- Use the preview result to verify that the field is output correctly.
Add alert labels
If you need to use other source data fields to filter or distinguish alerts, configure those fields as labels.
- Click Add Label to add a label configuration row.
- In Data Field, select a source field.
- In Label Key, enter the name used for this label in ONE.
- To remove the label, click Delete in its row.
- To add another label, click Add Label again.
Validation
Click "Execute Preview" to view the results in the data preview panel. In the execution preview state, this is a simulation of data processing, and no real data will be generated in the platform.