Chatta subito con l'assistenza
Chat con il supporto

Foglight for OpenStack 5.7.4 - User Guide

Using Foglight for OpenStack Interacting with Foglight for OpenStack dashboards Reference

Foglight tiles

The upper part of the tile displays the cloud infrastructure and a total count of these entries in the environment.

Figure 7. OpenStack Environment tiles displaying the cloud infrastructure

The lower part of the tile displays the count of entities at each severity level, based on the alarms currently active for those entities.

Figure 8. OpenStack Environment tiles: alarms

Clicking the label in the tile, for example, Availability Zones, displays summary and alarm information for all components of that type in the Quick View area.

Clicking the alarm count in the lower part of the tile displays summary and alarm information for only the components with that status.

Figure 9. OpenStack Environment: alarms displayed in Quick View

 

Interacting with Foglight for OpenStack dashboards

After installing Foglight for OpenStack, you can centrally manage your OpenStack cloud infrastructure resource objects. These resource objects include: Regions, Availability Zones, Host Aggregates, Hosts, Instances, and Volumes.

For more information, see these topics:

•
Interacting with Foglight for OpenStack
•
Preparing your OpenStack environment for monitoring
•
Using the OpenStack Environment dashboard
•
Exploring the OpenStack Environment Monitoring tab
•
Using the OpenStack Explorer dashboard

Interacting with Foglight for OpenStack

When you install Foglight for OpenStack, a set of predefined dashboards enables you to view the performance of your OpenStack system at a glance. Use the dashboards to ensure consistent application performance by drilling down on higher-level components such as Regions, Availability Zones, and Host Aggregates to view detailed specifics about each resource, such as CPU Utilization and Network Usage.

Foglight for OpenStack relies on Foglight Agents to collect data from monitored hosts, using a desired collection method. Prior to creating Foglight Agents, it is critical to properly configure the OpenStack environment for monitoring. For more information, see Preparing your OpenStack environment for monitoring .

The Administration tab of the OpenStack Environment dashboard lists the available Foglight Agents with their status. You can create agents and modify their properties here. For more information, see Administration tab .

In the navigation panel, under Dashboards, click OpenStack Environment to go to the OpenStack Environment dashboard. For more information about this dashboard and the associated views, see Using the OpenStack Environment dashboard .

To see in-depth details about an OpenStack cloud infrastructure resource, use the OpenStack Explorer dashboard. You can drill down for details from using the OpenStack Explorer Topology view in the navigation panel. For more information, see Using the OpenStack Explorer dashboard .

Preparing your OpenStack environment for monitoring

Prior to creating Foglight Agents, configure the servers that you want to monitor.

The following requirements must be met before the Foglight Agents can successfully collect data:

•
The OpenStack deployment is Liberty, Juno, Havana or Icehouse.
•
Endpoints (admin, public, and internal) are available for Keystone (by default, :35357, :5000), Nova (by default, :8774), Glance (by default, :9292), Cinder (by default, :8776), Neutron (by default, :9696).
•
The following ports are open on all hosts:
•
HTTPS (443)
•
SSH (22)
•
There is network visibility of compute nodes from the Foglight installation location.
Optional (for Instance Agents):
•
For Linux® instances:
•
Should be 64-bit.
•
Floating IP should be configured for instances to be visible from the host.
•
SSH port (default 22) should be open.
•
For Windows® instances:
•
Should be 64-bit.
•
Floating IP should be configured for instances to be visible from the host.
•
“Advanced” File and printer sharing should be enabled for administrator shares to be accessible from outside.
•
SMB ports should be open (netbios-ssn 139 and microsoft-ds 445).
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione