Skip to content

Metrics Management


After completing metrics data collection, you can view all reported measurements and their associated metrics, tags, time series statistics, daily day-over-day changes, and data storage policies in Metrics Management.

Measurement

A measurement is a collection of similar metrics, containing multiple metrics and tags. A single measurement displayed by the system includes the following information:

Metrics

Metrics reflect the operating status of a system (e.g., CPU usage, page load time, etc.) and consist of a metric name (identifier) and a metric value (specific numerical value).

Click the measurement name to view complete metric details (name/type/unit, etc.), and the following operations are supported:

  • Filter metrics based on keywords in the search bar;
  • Export the metric list as a CSV file;
  • In the operation column, support one-click metric analysis;
  • Click to expand metric data, where you can edit metric configuration.
Permissions and Priority
  • Edit permissions: Only standard members and above can operate;
  • Configuration priority: The unit and description customized in Metrics Management have higher priority than the default collected data. For example, after changing the unit from B to GB, chart queries in scenarios will automatically display data in GB.

Tags

The attributes of the data point collection object are identified through tags, which are presented as key-value pairs, consisting of a tag key and a tag value. A single data point can have multiple tags attached.

Click the measurement name to view the corresponding tag list, which includes information such as the tag key, tag value statistics count, and description. The following operations are supported:

  • Filter tags based on keywords in the search bar;
  • Export the tag list as a CSV file.

Time Series

Time series are dynamically generated from tag combinations and include metrics, tags (fields), and data storage duration. Here, "metric + tag (field combination)" constitutes the primary key for data storage.

In Guance, this section displays the total number of time series for the current measurement and presents the number of unique values, time series count, and daily day-over-day change for a single metric/tag through metric statistics charts and tag statistics charts.

Calculation Logic

The metric/tag statistics charts perform statistical calculations based on the hierarchy: Overall metrics → Single metric → Grouping of that metric by tags → Specific values of a tag → Global view of all tags + statistics of the tag itself.

In the statistics charts, the calculation logic for each field is as follows:

  • Number of unique values: The distinct count of the tag at the global or single metric dimension (i.e., how many non-repeating independent values this tag contains)
  • Number of time series: The number of time series designed for a single metric/single tag value
  • 1d: The change in the number of time series compared to the previous day
  • 1d%: 1d / Yesterday's time series count
  • Total proportion:
    • Metric level: The time series contained by this metric + tag / Total time series for this metric;
    • Tag level (single metric): Total time series for a single metric & single tag value / Total time series for a single metric & all tag values;
    • Tag value level: Time series designed for this tag value + this metric / Total time series for all values of this metric;
    • Tag level (full): Time series involving this tag value / Total time series for all values of this tag.
Term Description
Database A container database storing data
Measurement Measurement (similar to a MySQL table)
Field Metric key-value pair (stores actual values, not indexed)
Field Set A collection of multiple Fields
Field Key Key name of a Field (e.g., cpu_usage)
Field Value Value of a Field (e.g., 85.3)
Tag Tag key-value pair (descriptive metadata, indexed)
Tag Set A collection of multiple Tags
Tag Key Key name of a Tag (e.g., host)
Tag Value Value of a Tag (e.g., server-01)
TimeStamp Data point timestamp (nanosecond precision)
Retention Policy Data retention period (e.g., 30 days)
Series Unique time series (Measurement + Tag Set combination)

Storage Policy

The storage policy is divided into two levels:

Modifying Policy

The priority of custom settings for a measurement is higher than the workspace global settings. That is: After customizing the storage policy for a measurement, modifying the global settings will not affect that measurement.

Note

Each policy modification triggers immediate data deletion. Please back up important data in advance.

Precautions

When modifying the storage policy for a measurement, pay attention to the following key rules:

  1. Immediate data deletion: After modifying the policy, the data of this measurement under the original policy will be permanently deleted and cannot be recovered. Subsequent policy modifications will also delete the data under the current policy;
  2. Independent storage mechanism: After customizing the policy, the measurement data is stored independently. Modifying the global policy duration at this point will not affect measurements that have been customized;
  3. Reverting to global policy: When switching back to "Global Default", data will be stored back into the global repository. Subsequent modifications to the global policy will then affect this measurement;
  4. Same duration does not mean same policy: Even if the custom duration is the same as the global one, the data is still stored independently. Example: When the global is 7 days, setting a measurement to 7 days still constitutes independent storage.

Modification Path

Global Settings

Go to Manage > Workspace Settings > Risky Operations > Change Data Storage Policy > Metrics, and select the storage duration.

Measurement Custom Settings

Go to Metrics > Metrics Management, and in the operation column on the right side of a single measurement, click the icon to select the duration. If not set, it automatically inherits the Global Policy.

Important Limitations
  • Permission control: Only workspace owners can configure;
  • Data risk: Modifying the policy causes immediate and permanent deletion of data under the original policy.
Special Support for Deployment Plan

Custom duration: Supports entering any integer within the range of 1-1,800 days

Feedback

Is this page helpful? ×