The Ingress controller for Container Service for Kubernetes (ACK) streams all your HTTP request logs to standard output. ACK also integrates Ingress access logs with Simple Log Service, which allows you to quickly create dashboards for analysis and monitoring. This topic describes how to use the Ingress Dashboard with Application Real-Time Monitoring Service (ARMS) for troubleshooting.
Prerequisites
-
The log collection component is installed.
-
Log collection is enabled for Nginx Ingress.
Step 1: View Ingress logs and reports
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click Cluster Information.
-
Click the Basic Information tab. In the Cluster Resources section, click the project ID for Log Service Project.
-
In the left-side navigation pane, click the
icon. In the Dashboard list, view the Nginx Ingress analysis reports.The Ingress Dashboard provides five preset dashboards. This topic details two of them: Ingress Overview and Ingress Monitoring Center for blue-green deployment. For more information about the other preset dashboards, see Collect and analyze Nginx Ingress access logs.
-
Ingress Overview
The Ingress overview dashboard displays the overall status of the Nginx Ingress, including the following information:
Overall architecture status (1 day): includes page views (PVs), unique visitors (UVs), traffic, response latency, mobile client ratio, and error rate.
Real-time website status (1 minute): includes PVs, UVs, request success rate, average latency, P95 latency, and P99 latency.
User request information (1 day): includes 1-day PV comparison, 7-day PV comparison, geographic distribution, top provinces by access, top cities by access, mobile client ratio, and Android/iOS ratio.
Top URL statistics (1 hour): includes top 10 by access, top 10 by latency, top 10 by 5XX errors, and top 10 by 404 errors.
-
Ingress Monitoring Center for blue-green deployment
The Ingress blue-green deployment monitoring center provides real-time monitoring and comparison during version releases, including before-and-after comparisons and comparisons between the current blue and green versions. This helps you quickly detect anomalies and perform rollbacks during service releases. In this report, you must select the blue and green versions for comparison, such as ServiceA and ServiceB. The report dynamically displays relevant metrics for the selected versions, including PVs, 5XX rate, success rate, average latency, P95 latency, P99 latency, P999 latency, and traffic.
-
Step 2: Enable ARMS monitoring for a Java application
To enable ARMS monitoring for your Java application, see Java application monitoring.
Step 3: Configure an Ingress for the sample service
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click .
-
On the Ingresses page, click Create Ingress. Configure the Ingress and then click OK.
For more information about how to configure an Ingress, see Create and use an Nginx Ingress to expose services.
Step 4: Troubleshoot with Ingress Dashboard and ARMS
Log on to the Simple Log Service console.
-
In the Project list, click the name of the log project that you set during cluster creation. The default project name is k8s-log-{cluster-id}.
-
In the left-side navigation pane, click the
icon. In the Dashboard list, view the Ingress Overview V1.2 dashboard.For example, locate the Top 10 Request URLs by Latency section and view the URL(ARMS Troubleshooting) field. Click a URL to open the ARMS trace query page for the corresponding service, where you can view detailed trace information.