Converse agora com nosso suporte
Chat com o suporte

Foglight for Container Management 6.3.0 - User Guide

Understanding Foglight for Container Management Using Foglight for Container Management Reference

Optimizer

The Optimizer view appears after clicking Container > Kubernetes > Optimizer.

* 
NOTE: If the Optimizer tab is not displayed, ensure the following:
1. You have purchased a license for Optimizer. If not, contact Quest Support to purchase a license.
2. You have the Container Administrator role.
NOTE: The displayed views are varied if the cluster hosts are monitored by the agents of VMware, AWS, or Azure.
Figure 31. Kubernetes Optimizer Dashboard

The Optimizer view includes the following elements:

•
Settings. The Settings dialog box is used to change the time period and properties that are used for calculation. For more information, see Settings .
•
Automate. Use the Automate menu to set the criteria for automatically sending recommendations for improvements. Currently, this button only functions for CPU and Memory when a VMware cluster is selected.
•
Reclaim Now and Reclaim Later buttons. System administrator can select a VM from the list and review the Reclaiming Savings bar for information about how many resources can be reclaimed.
* 
NOTE: The Reclaim Now and Reclaim Later buttons are enabled only after selecting a checkbox from the table. Currently, the two buttons only function for VM Resources, CPU, and Memory when a VMware cluster is selected.
The Automate, Reclaim Now, and Reclaim Later buttons are displayed only when a VMware cluster is selected.
•
Exclude button. Select an object you want to exclude from the table to enable the Exclude button, and click Exclude. Then, this object is added to the list of excluded objects under a specific category.
•
Show Excluded Items button. Click the Show Excluded Items button to view the excluded objects. The Settings dialog box appears. For more information, see Excluded tab .
•
VM Resources/VM Resizing. Shows instance or virtual machine name, utilization, recommendations for both CPU and memory resources, and savings.
•
CPU. Shows instance or virtual machine name, utilization, recommendations for CPU resource, and estimated savings.
•
Memory. Shows instance or virtual machine name, utilization, recommendations for memory resource, and estimated savings.
•
Storage. Shows virtual machine name, utilization, storage and modify recommendations, and savings.
* 
NOTE: VM Resizing will be displayed when a cloud cluster is selected. VM Resources, CPU, Memory, and Storage will be displayed when a VMware cluster is selected.
•
Unused Resources table. Detects and shows those unused resources in container environment.
For example, persistent volume stays unused for more than 3 months. persistent volume stays in unbound status. This is due to the Unused Resources configuration in Settings.
•
Potential Zombies table. Detects and shows the potential pod controllers in container environment, including Deployment, Daemon Set, Stateful Set, Replication Controller, as well as Pod that is not managed by any Pod Controller.
For example, if all pods managed by a pod controller are zombies, then we might suggest you to delete the whole pod controller.

Settings

Use the Settings menu to define the default optimization settings for your environment. The Settings Dialog box provides information about the following components:

•
Configuration tab
•
Waste tab
•
Excluded tab
•
Credentials tab
•
Constraints tab
Configuration tab
Figure 32. Configuration tab

The Configuration tab provides the recommended settings for CPU, memory, and storage optimization.

•
Thresholds. Provides the values of a resource metric that define the Warning and Critical levels (for CPU, memory, and storage).
•
Recommendation Calculation area. Allows you to define the following parameters for optimizing the CPU, memory resources in your environment, Storage resources not supported at current version:

To save any changes made to the Configuration settings, click Save at the bottom of the tab.

Waste tab
Figure 33. Waste tab

The Waste tab allows you to configure the settings for determining resources wasted in your environment. These include unused resources and potential zombie Pod controllers.

•
Determine as waste if: used to filter Unused Resources.
•
Resource has been created [time] days: Resources that has been created more than the set days will be considered here.
•
Persistent Volume Status: By default, select Available and Failed. For detailed information, go to https://kubernetes.io/docs/concepts/storage/persistent-volumes/#phase.
•
Determine as a potential zombie if: used to filter Potential Zombies.
In container environment, Potential Zombie Pod Controller is considered here, including Deployment, Daemon Set, Stateful Set, Replication Controller, and Pod that is not managed by any Pod Controller. Settings work for single pod managed by Pod Controller. If all pods or partial pods of a Pod Controller are considered as zombies, different recommendations will be generated.
•
Time period used for average calculation is [time] days: The average metrics for the pods are calculated, so a time range should be set to calculate the average value.
•
Average resource utilization: only if a pod's metrics satisfy all the conditions, it will be considered to be a potential zombie pod.
•
Excluded Namespace: pods in the namespace can be excluded in the Potential Zombies check.

To save any changes made to the Waste settings, click Save at the bottom of the tab.

Excluded tab
Figure 34. Excluded tab

The Excluded tab allows you to remove a resource from the list of excluded objects. The Excluded tab includes the following information:

•
On the left side, a navigation tree, that allows you to select the resource category.
•
On the right side, the list of resources excluded from the selected category.

To remove resources from the list of Excluded objects, select the check boxes for these resources and click Remove. To save any changes made to the Excluded settings, click Save at the bottom of the tab.

The Excluded tab can also be accesses by clicking Show Excluded Items on the Optimizer tab.

Credentials tab
Figure 35. Credentials tab

This tab is available in VMware environment. The Credentials tab allows you to add, edit, and remove credentials groups. This tab is only for the Storage rightsizer.

Constraints tab
Figure 36. Constraints tab

This tab is available in VMware environment. The Constraints tab allows you to set custom thresholds for select objects in the environment. These recommendations are displayed in the Optimizer tab > VM Configuration/ CPU/ Memory/ Storage views > Modify Recommendation column. Use this tab to add, edit, and remove constraints groups.

* 
IMPORTANT: A virtual machine may have several partitions. VM environment makes recommendations for each partition separately, but the custom constraints can be set only for the entire VM (not for individual partitions). Therefore, the custom constraint for storage are applied to all partitions on the selected VM.

Administration

Figure 37. Kubernetes Administration Dashboard

 

* 
NOTE: The Administration dashboard can be accessed only when the users have both the Administrator role and the Container Administrator role. To grant the users with the Container Administrator role, go to Administration > Users & Security management under Administer Server > Manage Users, Groups, Roles > Roles tab.

 

* 
IMPORTANT: Heapster metrics collector is marked as Deprecated. Support for Heapster metrics collector will be removed in the future release. Users are encouraged to switch to the new Prometheus metrics collector.

The Administration dashboard supports new agent creation and existing agents management. It contains the following features:

•
Create Agent task
•
Remove Prometheus task
•
Agents table
Create Agent task

Use Create Agent or the Add button to start a wizard to create a new agent. See Creating and Activating a Kubernetes Agent for more information.

Remove Prometheus task

Remove Prometheus will start a wizard to remove the Prometheus successfully deployed through our platform.

* 
NOTE: Prometheus that are not deployed through our platform are not listed here.

Select the Prometheus you want to remove and click Remove.

* 
NOTE: All the related Kubernetes components will also be removed according to the template that you used to deploy the Prometheus through our platform.

If the Prometheus service is deleted successfully, a result message will be display. Otherwise, the Remove Prometheus wizard will appear again with error messages to guide you with further operations. Follow the messages and delete them again later.

Agents table

Use Activate, Deactivate, Start Data Collection, Stop Data Collection, Delete, and Update Agent to manage the agent.

Metrics Collector
•
Type: the type of Metrics Collector, supports Heapster, Prometheus, or OpenShift Prometheus.
•
Status:
•
Healthy: discovered the Kubernetes service of the Metrics Collector and the result for the health check of the service is successful.
•
Unhealthy: discovered the Kubernetes service of the Metrics Collector, however, the result for the health check of the service is failed.
•
Discover failed: failed to discover the Kubernetes service in your cluster. The Deploy icon is enabled.
•
Waiting for data update: waiting for status update after performing some operations for Metrics Collector.
•
Failed to update status: connection failed or other known issues. Contact the support.
•
Migrate : start a wizard to migrate Heapster to Prometheus Metrics Collector.
If the agent version is 3.0.0 and is using Heapster as the metric collector, you can Migrate from Heapster to Prometheus metrics collector.
•
Deploy : start a wizard to configure or guide to deploy Prometheus to your cluster.
If our platform failed to discover Prometheus in your cluster and the Deploy icon is enabled.
Migrate or Deploy process

Clicking Migrate or Deploy will launch the Configure Prometheus Metrics Collector Wizard.

•
Have existing Prometheus in your cluster.
* 
NOTE: Ensure that you have Prometheus in your cluster before this step. We will check the service existence and health status after you click Next.
•
Select the Prometheus Type.
•
Default type
Allows Agent to use KubeConfig credentials to access the Prometheus service. Enter the existing Prometheus service namespace and name to configure the metrics collector.
•
OpenShift Prometheus type: you need to provide OpenShift Route Hostname, Username, and Password for Agent to access the target OpenShift Prometheus.
* 
NOTE: To find the Route Hostname, go to the OPENSHIFT ORIGIN dashboard, Application > Routes.
Your OpenShift Login User should have the privilege to access to the Prometheus.
•
Do not have existing Prometheus in your cluster.
A Prometheus Configuration wizard will appear. To configure the metrics collector, either use the default Prometheus template or upload your own Prometheus deployment .yml files through Load from files.
* 
NOTE: Whenever you change the content in Configure file (template), ensure that the Namespace and Name fields are consistent with the Prometheus service configurations in your Configure file (template).
If you are using the default template, there is need to change anything.
Reset from template: Helps you to reset the Configure file (template) content to the default template.
Deploy: Creates Prometheus components to your cluster with the Configure file.
After clicking Deploy, a progress message will be displayed.
•
If deployed successfully, a succeeded message will be displayed. Close the Validation Result page and then click Next to finish your agent creation process.
•
If failed to deploy the Prometheus configuration, a Validation Result page will be displayed with possible solutions.
Agent Edit properties

Click in Properties column of the Agents table to edit the property of the agent.

•
For agent using Heapster as metric collector, a wizard similar as below will be displayed. Update the agent properties and save the changes. A new data collection process will be initiated.
•
For agent using Prometheus as metric collector and the Prometheus is successfully deployed through our platform, a wizard similar as below will be displayed.
* 
NOTE: If the Prometheus is deployed through our platform, the Service Namespace and Service Name cannot be updated through Kubernetes Agent Edit Properties wizard. You can use Remove Prometheus to remove Prometheus and deploy a new one.
Export: export the deployed .yml file of the Prometheus.
Change to Heapster: change from Prometheus Metrics Collector to Heapster. However, it is not recommended.
•
For agent using existing Prometheus as Metrics Collector, a wizard similar as below will be displayed.

 

* 
NOTE: If you are using your existing Prometheus as Metrics Collector, we will not help you to manage your Prometheus. Both the Service Namespace and Service Name can be updated in Kubernetes Agent Edit Properties wizard.
•
For agent using OpenShift Prometheus as Metrics Collector, a wizard similar as below will be displayed.

Docker Swarm

The Docker Container Quick View appears after clicking Monitoring > Containers. Click Swarm (Preview) from the header on top to switch to Docker Swarm dashboard.

Figure 38. Docker Swarm Dashboard

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação