You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
The number of active connections to envoy clusters is displayed differently in each data plane dashboard.
OSM Pod to Service Metrics irate(envoy_cluster_upstream_cx_active{source_pod_name="$source_pod",source_namespace="$source_namespace",envoy_cluster_name!~"osm-controller|envoy-metrics-cluster|envoy-tracing-cluster|passthrough-outbound"}[1m])
OSM Service to Service Metrics sum(envoy_cluster_upstream_cx_active{source_service="$source_service",source_namespace="$source_namespace",envoy_cluster_name="$destination_service"})
OSM Workload to Service Metrics envoy_cluster_upstream_cx_active{source_namespace="$source_namespace",source_workload_kind="$source_workload_kind",source_workload_name="$source_workload_name",envoy_cluster_name!~"osm-controller|envoy-metrics-cluster|envoy-tracing-cluster|passthrough-outbound"}"
Affected area (please mark with X where applicable):
Install [ ]
SMI Traffic Access Policy [ ]
SMI Traffic Specs Policy [ ]
SMI Traffic Split Policy [ ]
Permissive Traffic Policy [ ]
Ingress [ ]
Egress [ ]
Envoy Control Plane [ ]
CLI Tool [ ]
Metrics [ x ]
Certificate Management [ ]
Sidecar Injection [ ]
Logging [ ]
Debugging [ ]
Tests [ ]
Demo [ ]
CI System [ ]
Expected behavior:
The active connection graphs should display the current number of active connections from the source to any specified destination.
The text was updated successfully, but these errors were encountered:
Removes the irate function from the envoy cluster upstream active
connection query used in the OSM Pod to Service dashboard.
Resolvesopenservicemesh#4323
Signed-off-by: jaellio <[email protected]>
Removes the irate function from the envoy cluster upstream active
connection query used in the OSM Pod to Service dashboard.
Resolvesopenservicemesh#4323
Signed-off-by: jaellio <[email protected]>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description:
The number of active connections to envoy clusters is displayed differently in each data plane dashboard.
OSM Pod to Service Metrics
irate(envoy_cluster_upstream_cx_active{source_pod_name="$source_pod",source_namespace="$source_namespace",envoy_cluster_name!~"osm-controller|envoy-metrics-cluster|envoy-tracing-cluster|passthrough-outbound"}[1m])
OSM Service to Service Metrics
sum(envoy_cluster_upstream_cx_active{source_service="$source_service",source_namespace="$source_namespace",envoy_cluster_name="$destination_service"})
OSM Workload to Service Metrics
envoy_cluster_upstream_cx_active{source_namespace="$source_namespace",source_workload_kind="$source_workload_kind",source_workload_name="$source_workload_name",envoy_cluster_name!~"osm-controller|envoy-metrics-cluster|envoy-tracing-cluster|passthrough-outbound"}"
Affected area (please mark with X where applicable):
Expected behavior:
The active connection graphs should display the current number of active connections from the source to any specified destination.
The text was updated successfully, but these errors were encountered: