All Products
Search
Document Center

Container Service for Kubernetes:How to use Prometheus Service in a workflow cluster

Last Updated:Sep 24, 2025

A workflow cluster integrates with Application Real-Time Monitoring Service (ARMS) Prometheus Service to provide comprehensive observability. You can view the status of your workflows and the health of your cluster. This topic describes how to enable and use Prometheus Service in a workflow cluster.

Prerequisites

Billing

Monitoring a workflow cluster incurs additional fees. Before you enable this feature, carefully read the billing information.

Enable Prometheus Service

Enable through the console

  1. Log on to the ACK One console. In the navigation pane on the left, choose Workflow Cluster > Cluster Monitoring.

  2. On the Cluster Monitoring page, click Enable Workflow Cluster Monitoring. Then, click OK to enable monitoring for the workflow cluster.

Enable with a command

  1. Run the following command to retrieve the ClusterID of the workflow cluster.

    aliyun adcp DescribeHubClusters --Profile=XFlow
  2. Run the following command to enable Prometheus Service.

    aliyun adcp UpdateHubClusterFeature --MonitorEnabled true --ClusterId <cluster id>

    After you enable Prometheus Service, an ARMS Prometheus instance is automatically created for the workflow cluster.

View the Prometheus dashboard

  1. Log on to the ACK One console. In the navigation pane on the left, choose Workflow Cluster > Cluster Monitoring.

  2. On the Workflow Monitoring tab, click the Argo workflow monitoring dashboard to view the running status of workflows.

    123.png

Disable Prometheus Service

Shut down from the console

  1. Log on to the ACK One console. In the navigation pane on the left, choose Workflow Cluster > Cluster Monitoring.

  2. On the Cluster Monitoring page, click Disable Feature on the right. Then, click OK to disable monitoring for the workflow cluster.

Shut down using a command

  1. Run the following command to disable Prometheus Service.

aliyun adcp UpdateHubClusterFeature --MonitorEnabled false --ClusterId <cluster id>