지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Container Management 3.0 - User Guide

Health Check

Docker Container Status
Purpose

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

Scope

DockerContainer

Conditions and Severities
 

 
Conditions
Severity
Action

Container that is already stopped for abnormal reason.

Critical

Send email to Docker Swarm Administrator

Docker Container Status - Paused
Purpose

This rule detects abnormal long-time paused Container and fires alarm for different severity abnormal health status.

Scope

DockerContainer

Conditions and Severities
 

 
Conditions
Severity
Action

Container paused for two continuous data submission periods.

Warning

None

Docker Service Status
Purpose

This rule detects abnormal Docker Swarm Service health status and fires alarm for different severity abnormal health status.

Scope

DockerService

Conditions and Severities
 

 
Conditions
Severity
Action

Missing some of the replicated task running for this service.

Critical

Send email to Docker Swarm Administrator

Docker Task Status
Purpose

This rule detects abnormal Docker Swarm Task health status and fires alarm for different severity abnormal health status.

Scope

DockerTask

Conditions and Severities
 

 
Conditions
Severity
Action

Task that is in failed, orphaned or remove status.

Critical

Send email to Docker Swarm Administrator

Docker Task Status -- pending
Purpose

This rule detects abnormal long-time pending Docker Swarm Task and fires alarm for different severity abnormal health status.

Scope

DockerTask

Conditions and Severities
 

 
Conditions
Severity
Action

Task that is in pending status for two continuous data submission periods.

Warning

None

Usage

Docker Swarm Container CPU Utilization
Purpose

This rule detects abnormal CPU Utilization for Docker Swarm Containers, 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. This rule only works for those Containers that configures CPU limit.

Scope

DockerContainerCPU

Conditions and Severities
 

 
Conditions
Severity
Threshold (Registry Variable)*
Action

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

Fatal

Docker:ContainerCpuUtilizationFatal

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

Docker:ContainerCpuUtilizationCritical

None

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

Warning

Docker:ContainerCpuUtilizationWarning

None

*Note: the unit is percentage.
Docker Swarm Container Memory Utilization
Purpose

This rule detects abnormal Memory Utilization for Docker Swarm Containers, 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. This rule only works for those Containers that configures Memory limit.

Scope

DockerContainerMemory

Conditions and Severities
 

 
Conditions
Severity
Threshold (Registry Variable)*
Action

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

Fatal

Docker:ContainerMemoryUtilizationFatal

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

Docker:ContainerMemoryUtilizationCritical

None

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

Warning

Docker:ContainerMemoryUtilizationWarning

None

*Note: the unit is percentage.

Customization

To customize a rule, Rule Scope and Condition will be used frequently.

To access Rule Scope and Condition, do the following:
1
Under Dashboards, click Administration > Rules & Notifications > Rules, then click on the rule and select View and Edit.
2
Click Rule Editor on the Rule Detail popup dialog box. Then click Continue on the Confirm Edit Rule popup dialog box.
3
On the Rule Editor dashboard, Rule Scope can be located on the Rule Definition tab and Condition can be located on the Condition & Actions tab.
Figure 46. Rule Scope
Figure 47. Condition

Kubernetes

Filter Pods by Cluster

Finding Pods inside cluster “kubecluster”, enter following statement in the Scope of a rule, and choose KubePod as the Topology Type in the Rule Scope.

KubePod where namespace.cluster.name='kubecluster'

Filter Pods by Namespace

Finding Pods inside namespace “default” of Cluster “kubecluster”, enter following statement in the Scope of a rule, and choose KubePod as the Topology Type in the Rule Scope.

KubePod where namespace.cluster.name='kubecluster' and namespace.name='test'

Filter Nodes by Cluster

Finding Nodes inside cluster “kubecluster”, enter following statement in the Scope of a rule, and choose KubeNode as the Topology Type in the Rule Scope.

KubeNode where cluster.name='nancyakscluster'

Filter Pod by Labels

Find Pods with labels “run=nginx” and “env=prod” among all clusters, enter following statement in the Scope of a rule, and choose KubePod as the Topology Type in the Rule Scope.

KubePod where labels.key='run' and labels.value='nginx-rollingupdate' and labels.key=’env’ and labels.value=’prod’

If you want to find Pods by labels in namespace “test” of cluster “kubecluster”, you can append and namespace.cluster.name='kubecluster' and namespace.name='test' to the end of above statement.

Filter Node by Labels

Find Nodes with labels “env=prod” among all clusters, enter following statement in the Scope of a rule, and choose KubeNode as the Topology Type in the Rule Scope.

KubeNode where labels.key='env' and labels.value='prod'

If you want to find Nodes by labels in cluster “kubecluster”, you can append and cluster.name='kubecluster' to the end of above statement.

Filter Pod Metrics by Pod Labels

Find Pods Metrics with labels “run=nginx” and “env=prod” among all clusters, enter following statement in the Scope of a rule, and choose KubeHeapsterMetrics as the Topology Type in the Rule Scope.

KubePod.metrics where object.labels.key='run' and object.labels.value=’nginx’ and object.labels.key='env' and object.labels.value=’prod’

If you want to find Pods by labels in namespace “test” of cluster “kubecluster”, you can append and namespace.cluster.name='kubecluster' and namespace.name='test' to the end of above statement.

Filter Nodes Metrics by Node Labels

Find Node Metrics with labels “env=prod” among all clusters, enter following statement in the Scope of a rule, and choose KubeHeapsterMetrics as the Topology Type in the Rule Scope.

KubeNode.metrics where object.labels.key='env' and object.labels.value=’prod’

If you want to find Nodes by labels in cluster “kubecluster”, you can append and cluster.name='kubecluster' to the end of above statement.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택