Health Rules for Network Monitoring

This page describes the predefined health rules for the network connections in your Kubernetes® environment. To learn how to create and monitor health rules, see Entity Health Monitoring.

Predefined Health Rules for Network Monitoring

The Network Monitoring solution provides the following predefined health rules. You can use these health rules for a particular entity or modify them as custom rules based on your needs.

Health Rule Name	Description	Available for Entities	Enabled by Default
Network Connection TCP Health Rule	Determines if the TCP connection is unhealthy based on throughput, number of connections, RTT, retransmissions, SYN timeouts, and resets.	Network Connection	Yes
Network Connection DNS Health Rule	Determines if the DNS connection is unhealthy based on timeouts and response duration.	Network Connection	Yes
Network Connection UDP Health Rule	Determines if the UDP connection is unhealthy based on number of dropped connections.	Network Connection	Yes
Network Endpoint Incoming TCP Health Rule	Determines if the incoming TCP connections for the endpoint are unhealthy based on throughput and retransmissions.	Network Endpoint	Yes
Network Endpoint Outgoing TCP Health Rule	Determines if the outgoing TCP connections for the endpoint are unhealthy based on throughput and retransmissions.	Network Endpoint	Yes
Network Scope Incoming TCP Health Rule	Determines if the incoming TCP connections for the scope are unhealthy based on throughput and retransmissions.	Network Scope	Yes
Network Scope Outgoing TCP Health Rule	Determines if the outgoing TCP connections for the scope are unhealthy based on throughput and retransmissions.	Network Scope	Yes

Kubernetes® is a trademark of The Linux Foundation®.