Observability optimization
Posted: Thu Jan 23, 2025 9:19 am
1, 2, 3, and 4 in the figure represent the priority of the client accessing the service. When accessing a service, the priority is calculated based on the matching degree of the sub-zone, zone, and region, and then the service to be accessed is determined. The information in the service map is updated by the region-based priority information stored in the user state. The bpf program selects the corresponding endpoint to establish a link based on the priority information in the service map. In addition, Kmesh will update the endpoint_key in the endpoint map one by one during the load balancing policy update to ensure the continuity of the service during the update. Kmesh currently provides five different granularities of regional load balancing: region, zone, subZone, nodeName, and clusterID. It allows users to flexibly configure the load balancing policy that suits them.
With the region-based load balancing capability, Kmesh can more intelligently direct traffic to the best geographically located nodes, thereby reducing latency and improving service performance. This allows user requests to be responded to more quickly, which can significantly improve the overall user experience and network performance, especially for large-scale distributed applications across regions.
To improve the usability of Kmesh, the observability of Kmesh was also kazakhstan phone number data optimized in version v1.0 to meet user needs.
In Metrics, Kmesh optimizes the metrics labels, replacing the destination_service from the original destination in the socket to the final destination of this request. The original request from the source to the destination through the waypoint will be divided into two metrics: source->waypoint and waypoint->destination. The destination information is presented as the waypoint information.
before release v1.0
#destination_service_name is `reviews` instead of `reviews-svc-waypoint
kmesh_tcp_connections_closed_total{destination_app="reviews-svc-waypoint",destination_service="reviews-svc-waypoint
When multiple services share a waypoint, such metrics can confuse users. However, in v1.0.0, the destination_service of Kmesh metrics will always record the final destination information. The presented metrics are:
destination_service_name is `reviews` instead of `reviews-svc-waypoint`
kmesh_tcp_connections_closed_total{destination_app="reviews-svc-waypoint",destination_service_name="reviews
With this modification, a metric can include the destination information of this link and the final destination information. This makes the presented metrics more reasonable and easy to understand, and improves the overall clarity and usability of Kmesh observable data. In addition, Kmesh also works with Kiali to present users with a clear and intuitive service topology map.
With the region-based load balancing capability, Kmesh can more intelligently direct traffic to the best geographically located nodes, thereby reducing latency and improving service performance. This allows user requests to be responded to more quickly, which can significantly improve the overall user experience and network performance, especially for large-scale distributed applications across regions.
To improve the usability of Kmesh, the observability of Kmesh was also kazakhstan phone number data optimized in version v1.0 to meet user needs.
In Metrics, Kmesh optimizes the metrics labels, replacing the destination_service from the original destination in the socket to the final destination of this request. The original request from the source to the destination through the waypoint will be divided into two metrics: source->waypoint and waypoint->destination. The destination information is presented as the waypoint information.
before release v1.0
#destination_service_name is `reviews` instead of `reviews-svc-waypoint
kmesh_tcp_connections_closed_total{destination_app="reviews-svc-waypoint",destination_service="reviews-svc-waypoint
When multiple services share a waypoint, such metrics can confuse users. However, in v1.0.0, the destination_service of Kmesh metrics will always record the final destination information. The presented metrics are:
destination_service_name is `reviews` instead of `reviews-svc-waypoint`
kmesh_tcp_connections_closed_total{destination_app="reviews-svc-waypoint",destination_service_name="reviews
With this modification, a metric can include the destination information of this link and the final destination information. This makes the presented metrics more reasonable and easy to understand, and improves the overall clarity and usability of Kmesh observable data. In addition, Kmesh also works with Kiali to present users with a clear and intuitive service topology map.