This topic compares Kubernetes Monitoring, Application Monitoring, and Prometheus Service, and describes their relationships.

Relationships between Kubernetes Monitoring and other ARMS services

Relationships between Kubernetes Monitoring and other ARMS services
  • Application Monitoring focuses on the application frameworks and business codes that are used when applications are running. Kubernetes Monitoring focuses on the container control layer and system calls of containerized applications that run in containers. Both Application Monitoring and Kubernetes Monitoring are used to monitor applications. However, they focus on different layers of applications. The two services complement each other.
  • Kubernetes Monitoring focuses on the performance metrics of application layer protocols. It does not collect data such as traces, exception stacks, and JVM analysis.
  • Prometheus Service is the infrastructure for collecting, storing, and querying metrics. The metric data of Application Monitoring and Kubernetes Monitoring depends on Prometheus Service.

Comparison of Kubernetes Monitoring and Application Monitoring features

Feature Kubernetes Monitoring Application Monitoring
JVM monitoring ✔️
Trace query ✔️
Analysis on program exception stacks ✔️
Analysis on API error codes ✔️
Thread profiling ✔️
Arthas analysis ✔️
Kubernetes resource status monitoring ✔️
TCP call performance monitoring ✔️
Socket status monitoring ✔️
Network call packet analysis ✔️
DNS resolution performance monitoring ✔️
Process scheduling monitoring ✔️
Cloud service association ✔️

Comparison of Kubernetes Monitoring and Prometheus Service features

Feature Kubernetes Monitoring Prometheus Service
Metric time series ✔️ ✔️
Call details ✔️
Log query ✔️
Event statistics ✔️
Global topology ✔️