Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Foglight for Container Management 4.0 - User Guide

Table of Contents

Understanding Foglight for Container Management

About Foglight for Container Management Architecture Sizing Your Monitored Environment

Foglight Management Server Requirements Kubernetes Agent Requirements Docker Swarm Agent Requirements

Getting Started

Kubernetes Agent Docker Swarm Agent

Creating and Activating Agent

Creating and Activating a Kubernetes Agent Creating and Activating a Docker Swarm Agent

Configuring data collection interval

Using Foglight for Container Management

Monitoring Kubernetes Clusters

Kubernetes Clusters Summary view

Monitoring Kubernetes Nodes

Kubernetes Nodes Summary view

Monitoring Kubernetes Workloads

Kubernetes Workloads Summary view

Monitoring Kubernetes Pods

Kubernetes Pods Summary view

Monitoring Kubernetes Other Components

Configurations Storage Load Balancer

Alarms Capacity Management Cost Optimizer

Settings

Monitoring Docker Containers

Docker Container Summary view

Monitoring Docker Hosts

Docker Host Summary view

Monitoring Docker Swarm Clusters

Docker Swarm Cluster Summary view

Monitoring Docker Swarm Services

Docker Swarm Service Summary view

Kubernetes analytics

Heatmap analytics Scatter Plot analytics

Docker Swarm analytics

Heatmap analytics Scatter Plot analytics

Domains and Object Groups

Domains Object Groups

Kubernetes metrics

Workloads metrics Container metrics Node metrics

Docker Swarm metrics

Container metrics

Health Check Usage

Health Check Usage

Kubernetes Docker Swarm

Health Check

Docker Container Status

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

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

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

DockerContainer

Conditions and Severities


Conditions	Severity	Action
Container paused for two continuous data submission periods.	Warning	None

Docker Service Status

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

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

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

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

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

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

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

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

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

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 56. Rule Scope

Figure 57. 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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center