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
ifresp.StatusCode==http.StatusBadRequest&&bytes.Contains(bodyBytes, []byte("Kmesh monitoring is disable, cannot enable accesslog")) {
349
+
ifresp.StatusCode==http.StatusBadRequest&&bytes.Contains(bodyBytes, []byte("Kmesh monitoring is disable, cannot enable connectionMetrics")) {
350
350
log.Errorf("failed to enable connection metrics: %v. Need to start Kmesh's Monitoring. Please run `kmeshctl monitoring -h` for more help.", bodyString)
Copy file name to clipboardExpand all lines: docs/proposal/tcp_long_connection_metrics.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -171,19 +171,19 @@ We will update the functions of metric.go for periodic updating the workload and
171
171
172
172
#### Exposing long connection prometheus metrics
173
173
174
-
We will expose metrics for the connections whose duration exceesds 30 seconds. Not exposing metrics for short connection as it can lead to lot of metrics and they are also not suitable for prometheus metrics because prometheus itself has a scrape interval of maximum 15s, and short-lived connections may start and end between scrapes, resulting in incomplete or misleading data. By focusing only on longer-lived connections, we ensure the metrics are stable, meaningful, and better aligned with Prometheus’s time-series data model.
174
+
We will expose metrics for the connections whose duration exceeds 30 seconds. Not exposing metrics for short connection as it can lead to lot of metrics and they are also not suitable for prometheus metrics because prometheus itself has a scrape interval of maximum 15s, and short-lived connections may start and end between scrapes, resulting in incomplete or misleading data. By focusing only on longer-lived connections, we ensure the metrics are stable, meaningful, and better aligned with Prometheus’s time-series data model.
175
175
176
176
We can have a another component in future which reports realtime information about connections like cilium hubble.
177
177
178
178
Prometheus metrics exposed
179
179
180
-
- kmesh_tcp_connection_sent_bytes_total : The total number of bytes sent over established TCP connection
180
+
-`kmesh_tcp_connection_sent_bytes_total` : The total number of bytes sent over established TCP connection
181
181
182
-
- kmesh_tcp_connection_received_bytes_total : The total number of bytes received over established TCP connection
182
+
-`kmesh_tcp_connection_received_bytes_total` : The total number of bytes received over established TCP connection
183
183
184
-
- kmesh_tcp_connection_packet_lost_total : Total number of packets lost during transmission in a TCP connection
184
+
-`kmesh_tcp_connection_packet_lost_total` : Total number of packets lost during transmission in a TCP connection
185
185
186
-
- kmesh_tcp_connection_retrans_total : The total number of retransmits over established TCP connection
186
+
-`kmesh_tcp_connection_retrans_total` : The total number of retransmits over established TCP connection
0 commit comments