Cloud Service Mesh Dashboards and Support
1. Cloud Service Mesh Dashboards and Support
Service dashboards in Cloud Service Mesh provide critical service-level metrics for all services in your mesh. These dashboards provide insight into three of the four golden signals of monitoring-- latency, traffic, error, and saturation. This course does not go into detail about saturation. While a dedicated saturation metric might not exist, the CSM dashboard provides the essential metrics-- CPU, memory, latency, traffic-- needed to determine saturation. With these dashboards, you can define, review, and set alerts against Service Level Objectives, or SLOs, which summarize your service's user-visible performance. You can view detailed charts for individual services, filter the data, and drill into elements like response code, protocol, destination pod, and traffic source. Service endpoint information is also available, enabling you to observe traffic flow between services and communication performance. Service Level Indicators, or SLIs, are the key metrics you must report on, for example, latency and availability. After figuring out what to measure, SLIs, you can set targets for how good they need to be, SLOs. This helps you determine how much room for error you have, error budget. CSM provides a central, unified location for service operators to monitor and evaluate the health of their services. Alerts can be created to notify operators when an SLO has no more room for error. You can also visualize your mesh topology in CSM dashboards. Service charts are automatically generated and display the relationships and traffic flow between services. Finally, you can drill down into the workloads and pods of a service and queries per second rates between services. CSM is available with GKE or as a standalone offering on Google Cloud. Billing is determined by the Google APIs that are enabled on your project. When using Cloud Service Mesh as a standalone service, pricing is based on the number of clusters and the number of service mesh clients. Cloud Service Mesh as a standalone service includes Compute Engine VMs and GKE pods, telemetry dashboards with standard metrics-- custom metrics are charged based on cloud monitoring pricing-- a CSM-managed control plane, and Mesh CA, a managed certificate authority service with no per certificate charge. As of version 1.23, Cloud Service Mesh has some limitations compared to Istio. Limitations include service mesh integration with custom CAs. With Istio, you can set up your own custom root CA, which might manage identities both inside and outside of your cluster. Usage of Envoy filters to extend the service mesh for additional telemetry and policy. With Istio, you can extend the default functionality to provide additional checks at the networking layer. Usage of arbitrary telemetry and logging backends. CSM provides an out of the box integration with Google observability, but it's not possible to configure additional backends. While you can utilize the Prometheus metrics for your own monitoring solutions, the direct configuration of alternative logging or telemetry systems beyond Google's is not supported. Multi-network support and IPv6 for Kubernetes is also only available in Istio. And ambient mode data plane mode. With Istio, you can configure a per node layer for proxy and, optionally, a per namespace envoy proxy for layer 7 features instead of having a sidecar proxy on a per pod basis.2. Let's practice!
Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.