Metrics and Service Mesh
TOC
Using metrics
Monitoring plugin such as Prometheus or VictoriaMetrics should be installed to provide metrics for the Alauda Service Mesh v2 Operator and Istio control plane.
When you have added your application to the mesh, you can monitor the in-cluster health and performance of your applications running on Alauda Container Platform with metrics and customized alerts for CPU and memory usage, network connectivity, and other resource usage.
Configuring Monitoring with Service Mesh
You can integrate Alauda Service Mesh with user-workload monitoring to enable observability in your service mesh. User-workload monitoring provides access to essential built-in tools and is required to run Kiali, the dedicated console for Istio.
Prerequisites
- Alauda Service Mesh is installed.
Procedure
Create a YAML file named servicemonitor.yaml to monitor the Istio control plane:
Example ServiceMonitor object
Apply the YAML file by running the following command:
Create a YAML file named podmonitor.yaml to collect metrics from the Istio proxies (workloads):
Example PodMonitor object
- Specifies that the
PodMonitorobject must be applied in all mesh namespaces, including the Istio control plane namespace, because Alauda Container Platform monitoring ignores thenamespaceSelectorspec inServiceMonitorandPodMonitorobjects.
Apply the YAML file by running the following command:
Create a YAML file named asm-telemetry.yaml to configure prometheus metrics to istio proxies (workloads):
Example Istio Telemetry resource
- Add
mesh_idlabel to prometheus metrics.