Parameter | Description |
Task name | Specify the name of the export task. It can contain Chinese characters, letters (uppercase and lowercase), digits, and underscores (_), and must be 1 to 40 characters in length. |
workspace | Select the workspace for which you want to export data. Only a common workspace can be selected. tip Workspaces with a storage duration of 15 days or less support exporting only custom and other metrics, but not basic metrics. For details, see Metric references. |
Project | The project to which the export task belongs. Project management is a resource management method that allows you to manage cloud resources in groups based on different businesses or projects. Project-based authorization with Identity and Access Management (IAM) facilitates resource isolation and data security, as well as cost calculation across cloud resources. For details, see Project management. |
Tags | Labels are key-value pairs attached to export tasks to identify them. They can be used with selectors to quickly filter target export tasks. A tag is a key-value pair that allows you to classify and aggregate cloud resources from different dimensions. You can use tags for resource authorization and bill splitting. For details, see Managing labels. tip You can add up to 50 labels. |
Data filtering | Filter metrics in the workspace by using metric labels, such as job="prometheus" or __name__=~"job:.*". Regular expressions are supported. You can configure both AND rules and OR rules.
tip
|
Data query offset | Set the backward offset from the export timestamp to define the time range for raw metric queries. The offset can be accurate down to minutes and seconds. When exporting metrics from the workspace, the system queries the latest sample every minute based on the configured offset. If you encounter high data latency, we recommend increasing this query offset. |
Export target | Configure the destination for workspace data delivery. In this topic, TOS is selected as the destination. |
Target bucket | Select the destination bucket for workspace data delivery. |
Delivery directory | Select the root directory of the destination bucket for delivering workspace data. You can either select a file path or manually enter a path. |
Partition format | Naming convention for directories when data from your workspace is delivered to a destination bucket. TOS bucket directories are dynamically generated based on the creation time of delivery tasks. The value cannot start with a forward slash (/). The default value is %Y/%m/%d/%H/%M, which can generate a directory such as 2022/06/30/14/00. tip Prometheus involves time series monitoring data. When metrics are exported to TOS, the data is not piled into a single folder but organized into hierarchical directories based on time. |
Storage format | Data storage format. Currently, only the JSON format is supported. |
Compression type | The compression type for stored data. Supported compression types include snappy, gzip, and no compression. You can select the appropriate type based on your requirements.
|
Metric Relabel configuration | Configure metric relabeling. You can add labels to delivered metrics. For more details, refer to Metric relabeling. |