Skip to content

Metrics Management


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

Measurement

A measurement is a collection of similar metrics, containing multiple metrics and tags. The system displays the following information for each measurement:

Metrics

Metrics reflect the operational 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;
  • Perform one-click metric analysis in the operations column;
  • Click to expand metric data and edit metric configurations.
Permissions and Priority
  • Edit permissions: Only standard members and above can perform operations;
  • Configuration priority: Custom units and descriptions in Metrics Management take precedence over default collected data. For example, after changing the unit from B to GB, data in charts will automatically be displayed in GB.

Tags

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

Click the measurement name to view the corresponding tag list, including tag names, tag value statistics, descriptions, and more. 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 by tag combinations, containing metrics, tags (fields), and data storage duration. Here, "metric + tag (field combination)" forms the primary key for data storage.

In TrueWatch, the total number of time series for the current measurement is displayed here, and the unique value count, time series count, and daily changes for individual metrics/tags are presented through metric and tag statistical charts.

Calculation Logic

The metric/tag statistical charts are calculated based on the hierarchy of overall metric → individual metric → grouping by tags for that metric → specific tag values → global view of all tags + tag statistics.

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

  • Unique value count: The deduplicated count of tags globally or for a single metric (i.e., how many unique independent values the tag contains)
  • Time series count: 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 / the number of time series from the previous day
  • Total proportion:
    • Metric level: The time series included in the metric + tag / the total number of time series for the metric;
    • Tag level (single metric): The total number of time series designed for a single metric & single tag value / the total number of time series designed for a single metric & all tag values;
    • Tag value level: The time series designed for the tag value + the metric / the total number of time series for the metric value;
    • Tag level (full): The time series designed for the tag value / the total number of time series for the tag.
Term Description
Database A database container for storing data
Measurement A collection of metrics (similar to a MySQL table)
Field A key-value pair for metrics (stores actual numerical values, not indexed)
Field Set A collection of multiple Fields
Field Key The key name of a Field (e.g., cpu_usage)
Field Value The numerical value of a Field (e.g., 85.3)
Tag A key-value pair for tags (descriptive metadata, indexed)
Tag Set A collection of multiple Tags
Tag Key The key name of a Tag (e.g., host)
Tag Value The value of a Tag (e.g., server-01)
TimeStamp The timestamp of a data point (nanosecond precision)
Retention Policy The data retention period (e.g., 30 days)
Series A unique time series (Measurement + Tag Set combination)

Storage Policy

The storage policy is divided into two levels:

Modifying Policies

Custom settings for measurements take precedence over global workspace 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.

Key Considerations

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 for that measurement under the original policy will be permanently deleted and cannot be recovered. Subsequent policy modifications will also delete the current policy data;
  2. Independent storage mechanism: After customizing the policy, the measurement data will be stored independently. Modifying the global policy duration will not affect measurements with custom policies;
  3. Restoring global policy: When reverting to "global default," data will be stored in the global repository again. Subsequent global policy modifications will affect the measurement;
  4. Same duration does not mean the same policy: Even if the custom duration matches the global duration, the data is still stored independently. Example: When the global duration is 7 days, setting a measurement to 7 days still results in independent storage.

Modification Path

Global Settings

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

Custom Settings for Measurements

Go to Metrics > Metrics Management, and in the operations column on the right side of a 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 this;
  • Version limitation: The Free Plan does not support this feature;
  • Data risk: Modifying the policy results in the 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