Knative is a serverless application framework built on Kubernetes that establishes cloud-native serverless container orchestration standards. It helps you deploy and manage modern serverless workloads, enabling an enterprise-grade serverless container platform. Additionally, Alibaba Cloud has integrated Knative from its early versions, continuously synchronizing with Knative community features. Combined with Container Service for Kubernetes (ACK) and Alibaba Cloud messaging, storage, networking, and monitoring services, it provides production-ready Knative capabilities. You can integrate Knative into Managed Service for Prometheus to collect Knative metrics, helping you enhance service performance. This topic describes how to use Managed Service for Prometheus to monitor Knative.
Prerequisites
Managed Service for Prometheus is activated. For more information, see Billing overview.
An ACK cluster is created. For more information, see Create an ACK managed cluster, Create an ACK dedicated cluster, and Create an ACK Serverless cluster.
Knative is deployed in the cluster. For more information, see Deploy Knative.
Alibaba Cloud Resource Center is activated. For more information, see Activate Resource Center.
Procedure
Log on to the Managed Service for Prometheus console. In the left-side navigation pane, click Integration Center.
Click Knative. In the panel that appears, set the parameters as prompted.
metrics collection interval (seconds):
The interval for collecting monitoring data. The default value is 15.
The installed component is displayed on the Integration Management page in the Managed Service for Prometheus console. The Integration Management page consists of the Integrated Environments, Integrated Addons, and Query Dashboards tabs, where you can view information such as targets, metrics, dashboards, and alerts.
View the dashboard
On the Integrated Addons tab of the Integration Management page, click Knative to view the dashboard.
Knative monitoring data provided by Managed Service for Prometheus includes the request count, pod count, response time, and concurrent request count.
In the Overview section, you can view the request count, success rate of requests, 4xx errors (client errors), and 5xx errors (server errors).
NoteThe vertical axis indicates the number of requests processed per second. Unit: ops/sec.
In the Response Time section, you can view the response time percentiles, including the 50th, 90th, 95th, and 99th percentiles.
In the Autoscaler section, you can view the concurrent request count.
In the Resource Usages section, you can view the resource usage, including the CPU utilization and memory usage.
Key metrics
Metric | Description |
queue_average_concurrent_requests | The number of concurrent requests for the pod. |
queue_requests_per_second | The number of pod requests per second. |
revision_request_latencies | The response time. |
revision_request_count | The number of revision requests. |