Network
sysdig_connection_net_connection_in_count
| |
|---|
| Prometheus ID | sysdig_connection_net_connection_in_count |
| Legacy ID | net.connection.count.in |
| Metric Type | counter |
| Unit | number |
| Description | The number of currently established client (inbound) connections. |
| Additional Notes | net_connection* metric is especially useful when segmented by protocol, port or process. This is the TCP-level connection counts. Sysdig also performs heuristics to present UDP packets as connections based on src and dst IP for these. These calculation is depend on syscalls such as connect and accept. This is different from the net_request* metrics. They are calculated based on our classification of data by parsing read /write buffers associated with read/write and send/receive syscalls into request and response. Even though buffers are not evaluated to determine protocol-level info, Sysdig can determine that a request (for example, a certain server process has received a read syscall or a client process has sent a write syscall) has been made and an associated response has been sent. Using this information, Sysdig generates the metrics without protocol-level segmentation. The latency is determined using the time delta between a request and a response. |
sysdig_connection_net_connection_out_count
| |
|---|
| Prometheus ID | sysdig_connection_net_connection_out_count |
| Legacy ID | net.connection.count.out |
| Metric Type | counter |
| Unit | number |
| Description | The number of currently established server (outbound) connections. |
| Additional Notes | This metric is especially useful when segmented by protocol, port or process. |
sysdig_connection_net_connection_total_count
| |
|---|
| Prometheus ID | sysdig_connection_net_connection_total_count |
| Legacy ID | net.connection.count.total |
| Metric Type | counter |
| Unit | number |
| Description | The number of currently established connections. This value may exceed the sum of the inbound and outbound metrics since it represents client and server inter-host connections as well as internal only connections. |
| Additional Notes | This metric is especially useful when segmented by protocol, port or process. |
sysdig_connection_net_in_bytes
| |
|---|
| Prometheus ID | sysdig_connection_net_in_bytes |
| Legacy ID | net.bytes.in |
| Metric Type | counter |
| Unit | data |
| Description | The number of inbound network bytes. |
| Additional Notes | By default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI. |
sysdig_connection_net_out_bytes
| |
|---|
| Prometheus ID | sysdig_connection_net_out_bytes |
| Legacy ID | net.bytes.out |
| Metric Type | counter |
| Unit | data |
| Description | The number of outbound network bytes. |
| Additional Notes | By default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI. |
sysdig_connection_net_request_count
| |
|---|
| Prometheus ID | sysdig_connection_net_request_count |
| Legacy ID | net.request.count |
| Metric Type | counter |
| Unit | number |
| Description | The total number of network requests. Note, this value may exceed the sum of inbound and outbound requests, because this count includes requests over internal connections. |
| Additional Notes | |
sysdig_connection_net_request_in_count
| |
|---|
| Prometheus ID | sysdig_connection_net_request_in_count |
| Legacy ID | net.request.count.in |
| Metric Type | counter |
| Unit | number |
| Description | The number of inbound network requests. |
| Additional Notes | |
sysdig_connection_net_request_in_time
| |
|---|
| Prometheus ID | sysdig_connection_net_request_in_time |
| Legacy ID | net.request.time.in |
| Metric Type | counter |
| Unit | time |
| Description | The average time to serve an inbound request. |
| Additional Notes | |
sysdig_connection_net_request_out_count
| |
|---|
| Prometheus ID | sysdig_connection_net_request_out_count |
| Legacy ID | net.request.count.out |
| Metric Type | counter |
| Unit | number |
| Description | The number of outbound network requests. |
| Additional Notes | |
sysdig_connection_net_request_out_time
| |
|---|
| Prometheus ID | sysdig_connection_net_request_out_time |
| Legacy ID | net.request.time.out |
| Metric Type | counter |
| Unit | time |
| Description | The number of average time spent waiting for an outbound request. |
| Additional Notes | |
sysdig_connection_net_request_time
| |
|---|
| Prometheus ID | sysdig_connection_net_request_time |
| Legacy ID | net.request.time |
| Metric Type | counter |
| Unit | time |
| Description | The number of average time to serve a network request. |
| Additional Notes | |
sysdig_connection_net_total_bytes
| |
|---|
| Prometheus ID | sysdig_connection_net_total_bytes |
| Legacy ID | net.bytes.total |
| Metric Type | counter |
| Unit | data |
| Description | The total network bytes, including both inbound and outbound connections. |
| Additional Notes | By default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI. |