Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Foglight for Container Management 7.1.0 - User Guide

Understanding Foglight for Container Management Using Foglight for Container Management Reference

Health Check

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

DockerContainer

 

Container that is already stopped for abnormal reason.

Critical

Send email to Docker Swarm Administrator

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

DockerContainer

 

Container paused for two continuous data submission periods.

Warning

None

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

DockerService

 

Missing some of the replicated task running for this service.

Critical

Send email to Docker Swarm Administrator

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

DockerTask

 

Task that is in failed, orphaned or remove status.

Critical

Send email to Docker Swarm Administrator

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

DockerTask

 

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

Warning

None

Usage

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.

DockerContainerCPU

 

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

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.

DockerContainerMemory

 

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

Modifying alarms and threshold values

IMPORTANT: Avoid editing rules in the Administration > Rules & Notifications > Rule Management dashboard. Default rules may be modified during regular software updates and your edits will be lost. Always use the Alarm Templates dashboard.

You can and should modify the thresholds associated with alarms to better suit your environment. If you find that alarms are firing for conditions that you consider to be acceptable, you can change the threshold values that trigger the alarm. You can also enable or disable severity levels to better suit your environment.

When a rule has severity levels, a Threshold section appears in the Alarm Settings tab showing the severity levels and bounds by agent. Many rules, such as Baseline rules, do not have severity levels and thresholds.

When editing thresholds, ensure that the new values make sense in context with the other threshold values. For most metrics, threshold values are set so that Warning < Critical < Fatal. However, in metrics where normal performance has a higher value, the threshold values are reversed: Warning > Critical > Fatal.

IMPORTANT: The procedure below is a summary. Refer to Viewing, Creating, and Managing Alarm Templates in the Foglight 6.0 User Guide for more information on editing alarm templates for more information on working with alarm templates.
1
In the Navigation panel, click Alarm Templates.

Edit the rules using the procedure described in Viewing, Creating, and Managing Alarm Templates in the Foglight 6.0 User Guide

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 56. Rule Scope
Figure 57. Condition
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating