サポートと今すぐチャット
サポートとのチャット

Foglight for Container Management 4.0 - User Guide

Understanding Foglight for Container Management Using Foglight for Container Management Reference

Kubernetes

All rules are controlled by registry variable Kubernetes:AlertSensitivity. If the value is 0, then no alarm can be fired. If the value is 1, warning level alarm can be fired. If the value is above 1, then all level alarm can be fired.

Kubernetes Administrator email address can be configured in Registry Variable KubernetesAdmin.

Health Check

This rule detects abnormal Pod health status and fires alarm for different severity abnormal health status.

KubePod

 

Pods that is in Failed or Unknown status. Or the node which is running the pod gets disconnected.

Critical

Send email to Kubernetes Administrator.

Pods that is in CrashLoopBackOff status.

Warning

None

This rule detects Pods that stays in pending phase for an abnormal long time.

KubePod

 

Pods that is pending for two continuous data submission periods because of Failed to schedule to Node.

Critical

Send email to Kubernetes Administrator.

Pods that is pending for two continuous data submission periods because container is not ready.

Warning

None

This rule detects abnormal Container health status and fires alarm for different severity abnormal health status.

KubeContainer

 

Container that is terminated for abnormal reasons.

Critical

Send email to Kubernetes Administrator.

This rule detects abnormal Node health status and fires alarm for different severity abnormal health status.

KubeNode

 

Nodes that is not Ready or out of disk or network unavailable.

Critical

Send email to Kubernetes Administrator.

Nodes whose memory or disk is under pressure.

Warning

None

This rule detects abnormal Deployment health status and fires alarm for different severity abnormal health status.

KubeDeployment

 

Deployment is not available.

Critical

Send email to Kubernetes Administrator.

Deployment has failed to create some of the replicated pods.

Warning

None

This rule detects abnormal Daemon Set health status and fires alarm for different severity abnormal health status.

KubeDaemonSet

 

Some of the pods created by the Daemon Set is not available or mis-scheduled.

Critical

Send email to Kubernetes Administrator.

The daemon set doesn’t have enough replicated pods running that meets its desired replicated pods count.

Warning

None

This rule detects abnormal Job health status and fires alarm for different severity abnormal health status.

KubeJob

 

Job that is failed.

Warning

None

This rule detects abnormal Persistent Volume health status and fires alarm for different severity abnormal health status.

KubePersistentVolume

 

Persistent Volume that is in failed status.

Warning

None

This rule detects abnormal Persistent Volume Claim health status and fires alarm for different severity abnormal health status.

KubePersistentVolumeClaim

 

Persistent Volume Claim that is in failed status.

Warning

None

This rule detects abnormal long pending Persistent Volume Claim and fires alarm for different severities.

KubePersistentVolumeClaim

 

Persistent Volume Claim that is pending for two continuous data submission periods.

Critical

None

This rule checks for container that restarted and previously terminated in an invalid state within the last 12 hours.

KubeContainer

 

Container that restarted and previously terminated in an invalid state within the last 12 hours.

Critical

Send email to Kubernetes Administrator

 

Usage

 

This rule detects abnormal CPU Utilization for Pods, and fires alarm on different severities. It is disabled by default. You can customize it and enable it based on your different requirements. For more details about customization, refer to Customization . You can also change value of the registry variables or use your own value to change the threshold of each severities. This rule only works for those Pods that configures CPU limit.

KubePodCpu

 

Pods whose usage is about to reach the limit, the ration is above the value configured in fatal Threshold.

Fatal

Kubernetes:PodCpuUtilizationFatal

Send email to Kubernetes Administrator

Pods whose usage is about to reach the limit, the ration is above the value configured in critical Threshold.

Critical

Kubernetes:PodCpuUtilizationCritical

None

Pods whose usage is about to reach the limit, the ration is above the value configured in warning Threshold.

Warning

Kubernetes:PodCpuUtilizationWarning

None

This rule detects abnormal Memory Utilization for Pods, and fires alarm on different severities. It is disabled by default. You can customize it and enable it based on your different requirements. For more details about customization, refer to Customization . You can also change value of the registry variables or use your own value to change the threshold of each severities. This rule only works for those Pods that configures Memory limit.

KubePodMemory

 

Pods whose usage is about to reach the limit, the ration is above the value configured in fatal Threshold.

Fatal

Kubernetes:PodMemoryUtilizationFatal

Send email to Kubernetes Administrator

Pods whose usage is about to reach the limit, the ration is above the value configured in critical Threshold.

Critical

Kubernetes:PodMemoryUtilizationCritical

None

Pods whose usage is about to reach the limit, the ration is above the value configured in warning Threshold.

Warning

Kubernetes:PodMemoryUtilizationWarning

None

This rule detects abnormal CPU Usage for Pods, and fires alarm on different severities. It is disabled by default. You can customize it and enable it based on your different requirements. For more details about customization, refer to Customization . You can also change value of the registry variables or use your own value to change the threshold of each severities.

KubePodCpu

 

Pods whose usage is above the value configured in fatal Threshold.

Fatal

Kubernetes:PodCpuUsageFatal

Send email to Kubernetes Administrator

Pods whose usage is above the value configured in critical Threshold.

Critical

Kubernetes:PodCpuUsageCritical

None

Pods whose usage is above the value configured in warning Threshold.

Warning

Kubernetes:PodCpuUsageWarning

None

This rule detects abnormal Memory Usage for Pods, and fires alarm on different severities. It is disabled by default. You can customize it and enable it based on your different requirements. For more details about customization, refer to Customization . You can also change value of the registry variables or use your own value to change the threshold of each severities.

KubePodMemory

 

Pods whose usage is above the value configured in fatal Threshold.

Fatal

Kubernetes:PodMemoryUsageFatal

Send email to Kubernetes Administrator

Pods whose usage is above the value configured in critical Threshold.

Critical

Kubernetes:PodMemoryUsageCritical

None

Pods whose usage is above the value configured in warning Threshold.

Warning

Kubernetes:PodMemoryUsageWarning

None

This rule detects abnormal Network Receive Rate in bytes/second for Pods, and fire alarm on different severities. It is disabled by default. You can customize it and enable it based on your different requirements. For more details about customization, refer to Customization . You can also change value of the registry variables or use your own value to change the threshold of each severities.

KubePodNetwork

 

Pods whose usage is above the value configured in fatal Threshold.

Fatal

Kubernetes:PodNetworkReceiveFatal

Send email to Kubernetes Administrator

Pods whose usage is above the value configured in critical Threshold.

Critical

Kubernetes:PodNetworkReceiveCritical

None

Pods whose usage is above the value configured in warning Threshold.

Warning

Kubernetes:PodNetworkReceiveWarning

None

This rule detects abnormal Network Send Rate in bytes/second for Pods, and fire alarm on different severities. It is disabled by default. You can customize it and enable it based on your different requirements. For more details about customization, refer to Customization . You can also change value of the registry variables or use your own value to change the threshold of each severities.

KubePodNetwork

 

Pods whose usage is above the value configured in fatal Threshold.

Fatal

Kubernetes:PodNetworkSendFatal

Send email to Kubernetes Administrator

Pods whose usage is above the value configured in critical Threshold.

Critical

Kubernetes:PodNetworkSendCritical

None

Pods whose usage is above the value configured in warning Threshold.

Warning

Kubernetes:PodNetworkSendWarning

None

This rule checks kubernetes pod filesystem utilization to see if it reaches the defined threshold. The filesystem utilization rule only works for pod that configures filesystem limit.

KubePodStorage

 

Pods whose usage is about to reach the limit, the ration is above the value configured in fatal Threshold.

Fatal

Kubernetes: PodFilesystemUtilizationFatal

Send email to Kubernetes Administrator

Pods whose usage is about to reach the limit, the ration is above the value configured in critical Threshold.

Critical

Kubernetes: PodFilesystemUtilizationCritical

None

Pods whose usage is about to reach the limit, the ration is above the value configured in warning Threshold.

Warning

Kubernetes: PodFilesystemUtilizationWarning

None

This rule detects abnormal CPU Utilization for Nodes, and fire alarm on different severities. It is enabled by default. You can change value of the registry variables or use your own value to change the threshold of each severities.

KubeNodeCpu

 

Nodes whose utilization is above the value configured in fatal Threshold.

Fatal

Kubernetes:NodeCpuUtilizationFatal

Send email to Kubernetes Administrator

Nodes whose utilization is above the value configured in critical Threshold.

Critical

Kubernetes:NodeCpuUtilizationCritical

None

Nodes whose utilization is above the value configured in warning Threshold.

Warning

Kubernetes:NodeCpuUtilizationWarning

None

This rule detects abnormal Memory Utilization for Nodes, and fire alarm on different severities. It is enabled by default. You can change value of the registry variables or use your own value to change the threshold of each severities.

KubeNodeMemory

 

Nodes whose utilization is above the value configured in fatal Threshold.

Fatal

Kubernetes:NodeMemoryUtilizationFatal

Send email to Kubernetes Administrator

Nodes whose utilization is above the value configured in critical Threshold.

Critical

Kubernetes:NodeMemoryUtilizationCritical

None

Nodes whose utilization is above the value configured in warning Threshold.

Warning

Kubernetes:NodeMemoryUtilizationWarning

None

This rule detects abnormal Network Receive Rate in bytes/second for Nodes, and fire alarm on different severities. It is enabled by default. You can change value of the registry variables or use your own value to change the threshold of each severities.

KubeNodeNetwork

 

Nodes whose utilization is above the value configured in fatal Threshold.

Fatal

Kubernetes:NodeNetworkReceiveFatal

Send email to Kubernetes Administrator

Nodes whose utilization is above the value configured in critical Threshold.

Critical

Kubernetes:NodeNetworkReceiveCritical

None

Nodes whose utilization is above the value configured in warning Threshold.

Warning

Kubernetes:NodeNetworkReceiveWarning

None

This rule detects abnormal Network Send Rate in bytes/second for Nodes, and fire alarm on different severities. It is enabled by default. You can change value of the registry variables or use your own value to change the threshold of each severities.

KubeNodeNetwork

 

Nodes whose utilization is above the value configured in fatal Threshold.

Fatal

Kubernetes:NodeNetworkSendFatal

Send email to Kubernetes Administrator

Nodes whose utilization is above the value configured in critical Threshold.

Critical

Kubernetes:NodeNetworkSendCritical

None

Nodes whose utilization is above the value configured in warning Threshold.

Warning

Kubernetes:NodeNetworkSendWarning

None

Periodically check Kubernetes node Network Transfer Rate in bytes/second, if the value is too high and changes too much, then an alarm will be triggered.

KubeNodeNetwork

 

Nodes whose usage is about to reach the limit, the ration is above the value configured in fatal Threshold.

Fatal

Kubernetes: NodeNetworkTransferFatal

Send email to Kubernetes Administrator

Nodes whose usage is about to reach the limit, the ration is above the value configured in critical Threshold.

Critical

Kubernetes: NodeNetworkTransferCritical

None

Nodes whose usage is about to reach the limit, the ration is above the value configured in warning Threshold.

Warning

Kubernetes: NodeNetworkTransferWarning

None

*Note: the unit is bytes/second.

Periodically check Kubernetes node Filesystem Utilization, if the value is too high and changes too much, then an alarm will be triggered.

KubeNodeFilesystem

 

Nodes whose usage is about to reach the limit, the ration is above the value configured in fatal Threshold.

Fatal

KubeNodeFilesystemUtilizationFatal

Send email to Kubernetes Administrator

Nodes whose usage is about to reach the limit, the ration is above the value configured in critical Threshold.

Critical

KubeNodeFilesystemUtilizationCritical

None

Nodes whose usage is about to reach the limit, the ration is above the value configured in warning Threshold.

Warning

KubeNodeFilesystemUtilizationWarning

None

*Note: the unit is percentage.

This rule checks Kubernetes container CPU utilization to see if it reaches the defined threshold. The CPU utilization rule only works for container that configures CPU limit.

KubeContainerCpu

 

Containers whose usage is about to reach the limit, the ration is above the value configured in fatal Threshold.

Fatal

Kubernetes:ContainerCpuUtilizationFatal

Send email to Kubernetes Administrator

Containers whose usage is about to reach the limit, the ration is above the value configured in critical Threshold.

Critical

Kubernetes:ContainerCpuUtilizationCritical

None

Containers whose usage is about to reach the limit, the ration is above the value configured in warning Threshold.

Warning

Kubernetes:ContainerCpuUtilizationWarning

None

*Note: the unit is percentage.

This rule checks Kubernetes container Memory utilization to see if it reaches the defined threshold. The Memory utilization rule only works for container that configures Memory limit.

KubeContainerMemory

 

Containers whose usage is about to reach the limit, the ration is above the value configured in fatal Threshold.

Fatal

Kubernetes: ContainerMemoryUtilizationFatal

Send email to Kubernetes Administrator

Containers whose usage is about to reach the limit, the ration is above the value configured in critical Threshold.

Critical

Kubernetes: ContainerMemoryUtilizationCritical

None

Containers whose usage is about to reach the limit, the ration is above the value configured in warning Threshold.

Warning

Kubernetes: ContainerMemoryUtilizationWarning

None

*Note: the unit is percentage.

Purpose

Detecting container cluster whose budget is over spending.

Scope

AbstractKubernetesClusterCost

 

Cluster current month cost which is about to reach the limit, the ration is above the value configured in fatal Threshold.

Fatal

ContainerCost:OverBudgetFatal

ContainerCostAdmin

Send email to Kubernetes Administrator

Cluster current month cost which is about to reach the limit, the ration is above the value configured in critical Threshold.

Critical

ContainerCost:OverBudgetCritical

None

Cluster current month cost which is about to reach the limit, the ration is above the value configured in warning Threshold.

Warning

ContainerCost:OverBudgetWarning

None

*Note: the unit is percentage.

Docker Swarm

All rules are controlled by registry variable Docker:AlertSensitivity. If the value is 0, then no alarm can be fired. If the value is 1, warning level alarm can be fired. If the value is above 1, then all level alarm can be fired.

Docker Swarm Administrator email address can be configured in Registry Variable Docker:DockerAdmin.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択