All Products
Search

This Product

    Application Real-Time Monitoring Service:Abnormal monitoring data after changing a cluster or namespace

    Document Center

    Application Real-Time Monitoring Service:Abnormal monitoring data after changing a cluster or namespace

    Last Updated:Jun 20, 2026

    Symptoms

    • After you change an application's namespace, the service name prefix on a custom metrics dashboard does not update.

      For example, the namespace column is updated to arms-test, but the service column still shows arms-demo:mall-gateway. The prefix is not updated to arms-test.

    • After you change the application's cluster, RED metrics are displayed correctly, but container monitoring shows no data for CPU and memory.

    Possible cause

    ARMS writes container-related information, such as the namespace and ClusterId, to the configuration when an application is created. This configuration does not update automatically. Consequently, if you change the application's cluster or namespace, ARMS may fail to retrieve or display the corresponding container data.

    Solutions

    • Delete the application, create a new one, and then report the monitoring data again. For more information, see Delete an application.

      This method deletes the application's historical data.

    • Submit a ticket.