How Do I Query Application Metrics in AOM?

Procedure

After application metrics are enabled for a service mesh that has been connected to Huawei Cloud Application Operations Management (AOM), you can query the application metrics in AOM.

1. Log in to the AOM console and choose Metric Browsing.
2. Click the Metric Sources tab and select the target Prometheus instance.

   

3. Query metrics reported to AOM.
   • All metrics

   You can enter a metric name to query metrics.

   In addition, you can add conditions to query related information.

   • Prometheus statement

   Enter the PromQL statement to query metrics.

Application Metric Labels

• reporter: the reporter of request metrics. If metrics are reported by the Istio proxy on the server, set it to destination. If metrics are reported by the Istio proxy or gateway on the client, set it to source.
• source_workload: the name of the source workload. If the source information is missing, the value is unknown.
• source_workload_namespace: the namespace of the source workload. If the source information is missing, the value is unknown.
• source_app: the source application identified by the app label of the source workload. If the source information is missing, the value is unknown.
• source_version: the version of the source workload. If the source information is missing, the value is unknown.
• destination_workload: the name of the destination workload. If the destination information is missing, the value is unknown.
• destination_workload_namespace: the namespace of the destination workload. If the destination information is missing, the value is unknown.
• destination_app: the destination application identified by the app label of the destination workload. If the destination information is missing, the value is unknown.
• destination_version: the version of the destination workload. If the destination information is missing, the value is unknown.
• destination_service: the destination host responsible for incoming requests, for example, details.default.svc.cluster.local.
• destination_service_name: the name of the destination service, for example, details.
• destination_service_namespace: the namespace of the destination service.
• request_protocol: the protocol of requests. Set it to the protocol of the requests or connections.
• response_code: the response code of the requests. This label is only displayed when the protocol is HTTP.
• connection_security_policy: the service authentication policy of the requests. When Istio uses security policies to ensure communication security and metrics are reported by the Istio proxy on the server, set it to mutual_tls. When metrics are reported by the Istio proxy on the client, set it to unknown because security policies cannot be properly defined.
• destination_cluster: the cluster name of the destination workload.
• source_cluster: the cluster name of the source workload.
• grpc_response_status: the response status of gRPC. This label is only displayed when the protocol is gRPC.
• destination_pod: the pod name of the destination workload.
• destination_port: the port of the destination service.