After you install a probe for an application, Cloud Monitor 2.0 starts monitoring it. The Application list page displays basic application metrics, such as the number of requests, error rate, and response time.
Try the feature
Alibaba Cloud Playground provides a demo environment where you can experience the main features of Cloud Monitor 2.0.
Go to the Playground Demo environment. By default, you are logged on to the following workspace:
o11y-demo-cn-hangzhou.In the navigation pane on the left, choose .
Page description
Log on to the Cloud Monitor 2.0 console, and select a workspace. In the left navigation pane, choose .
The Application list page displays basic metrics for all connected applications, including the average number of requests, average number of errors, and average latency.
At the top of the page, you can filter applications by query condition or keyword.
You can click an application name to view its detailed data and configure custom settings.
You can hover the mouse pointer over a parameter in the list to perform quick operations.
: Preview entity. You can view basic information about the entity in the panel that appears.
: Send to Copilot. You can use O&M Assistant to analyze issues related to the current parameter.
: Copy the current parameter name.
: View information about entities associated with the current application, such as Kubernetes pods, APIs, and instances.
: Open the link for the current parameter to view more details.
FAQ
Why do duplicate application names appear?
Duplicate application names can occur in the following two scenarios:
Applications from different sources have the same name. For example, an application created by integrating ARMS with a product such as EDAS or SAE may have the same name as an application that a user manually connected to ARMS.
Two applications that use different language frameworks have the same name.
A RAM user cannot see applications on the Application list page
The `ReadOnlyAccess` or `AliyunARMSReadOnlyAccess` system policy only allows a Resource Access Management (RAM) user to log on to the ARMS console. These policies do not grant the permission to view applications. You must grant the `ReadTraceApp` permission for a specific resource group. Without this permission, ARMS cannot display the application list because resource group authorization is required. For more information, see Custom RAM authorization policies for Application Monitoring.
When you add the `ReadTraceApp` access policy for the user, set the resource scope to the resource group level.
Complete example:
