All Products
Search
Document Center

Application Real-Time Monitoring Service:Why is monitoring data abnormal after the application changes the cluster or namespace?

Last Updated:Mar 11, 2026

After you change the cluster or namespace of an application, some monitoring data in Application Real-Time Monitoring Service (ARMS) may display incorrectly. ARMS records container-related parameters such as Namespace and ClusterId at application creation time and does not update them automatically.

Symptoms

You may notice one or both of the following issues:

  • The namespace column on a custom dashboard still shows the old value. The dashboard displays the previous namespace after the change.

    Namespace column showing outdated value on a custom dashboard

  • Container monitoring metrics are missing, but RED metrics display normally. Rate, errors, and duration (RED) metrics work as expected, while container-level metrics such as CPU and memory show no data.

Possible cause

When you create an application in ARMS, the system stores container-related parameters, including Namespace and ClusterId, as static values. These values cannot be automatically updated.

If you change the cluster or namespace of your application, the container-related data may fail to be queried or displayed.

Solutions

Option 1: Delete and recreate the application

Warning

This method causes the loss of historical monitoring data. If you need to retain historical data, use Option 2 instead.

  1. Delete the application from ARMS. For more information, see Delete applications.

  2. Recreate the application in the new cluster or namespace.

  3. Report monitoring data again.

Option 2: Submit a ticket

Submit a ticket to contact Alibaba Cloud technical support for assistance.