Docs

Volcengine Managed Service for Prometheus

Creating a workspace

Creating local workspaces

The local workspace allows you to associate your self-built or external Prometheus instances in the Volcengine Managed Service for Prometheus (VMP) console. This topic describes the procedure and considerations for creating a local workspace.

tip

[Beta · Apply for Trial]: This feature is currently in beta. If you want to use it, contact your account manager.

Prerequisites

An external Prometheus instance has been created or obtained.

If the self-built Prometheus instance is located inside the VPC, the Query address must be configured for the instance.

If the external Prometheus instance is deployed in an Internet data center (IDC) or another cloud provider:

No additional configuration is required when the external Prometheus instance has a public network address.

You need to first use Cloud Enterprise Network (CEN) to establish network connectivity and allow inbound traffic from the selected VPC CIDR block when the external Prometheus instance does not have a public network address.

tip

When you associate a local workspace with a self-built Prometheus instance in an Elastic Compute Service (ECS) instance, you need to configure a security group for the ECS instance to allow traffic from the security groups and ports of the local workspace. For more details, refer to Using a local workspace to associate a local Prometheus instance.

Procedure

In the top navigation bar, select the target region.

Click Workspace in the left navigation bar to go to the workspace list page.

Click Create, and click the Local workspace tab to configure the local workspace.

Basic information

Parameter	Descriptions
Name	Specify the name of the workspace. The name can contain Chinese characters, uppercase letters and lowercase letters, digits, periods (.), underscores (_), and hyphens (-). The name must be 1 to 100 characters in length.
Project	The project to which the workspace belongs. Project management is a resource management mechanism that Volcano Engine provides to enable grouping of cloud resources by project. 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.
Tag	Add labels to the workspace. A label is used to identify the workspace. You can combine labels with selectors to filter workspaces. A label is a key-value pair that allows you to classify and aggregate cloud resources from different dimensions. You can use labels for resource authorization and bill splitting. For details, see Managing labels. tip You can add up to 50 labels.
Address	Specify a query URL for the self-built Prometheus instance. The address must start with HTTPS or HTTP. The address must be up to 1,000 characters in length.
Description	Specify the description of the workspace. The description can contain Chinese characters, letters, digits, and special characters. The description must be 1 to 200 characters in length.

Permissions and network

Parameter	Descriptions
Authentication method	Specify an authentication method for the custom Prometheus instance. Valid values: Basic auth: The username and password are used for authentication. When you select this method, you need to configure the username and password for your custom Prometheus instance. Bearer token: A token is used for authentication. When you select this method, you need to configure an authentication token for your custom Prometheus instance.
Custom HTTP Header	Configure custom HTTP headers. The HTTP header is in the format of header and value. The header can contain Chinese characters, letters, and special characters and must be 1 to 200 characters in length. tip You can configure up to 10 groups of HTTP headers for the local workspace.
Network Configuration	You can configure one of the following methods of accessing the self-built Prometheus instance: Public network: You can choose this method when your self-built Prometheus instance is located in an IDC or another cloud provider, and can be accessed over the public network. Private network: You can choose this method when your self-built Prometheus instance is located in a Volcano Engine VPC, or is located at another cloud provider but is connected to the Volcano Engine VPC via a dedicated line. When you select Private VPC access, you need to specify a VPC and its subnet.

Click Submit to complete the configuration.

Connectivity test

After the configuration is complete, click the workspace name to go to the Overview page of the workspace. Click Connectivity Test to ensure that the configured local workspace can access the self-built Prometheus instance.

What to do next

The local workspace does not provide an access address and does not support metric queries through the Explore feature in the console. To query the metrics stored in the local workspace, you need to add the local workspace to the aggregation workspace and query metrics through the aggregation workspace. For details, see Creating aggregation query workspaces.

Last updated: 2026.07.10 11:37:25