Chat now with support
Chat with Support

Foglight Hybrid Cloud Manager 7.1.0 - User Guide (for AWS environments)

Using Foglight Hybrid Cloud Manager for AWS Monitoring Tab System Info Tab Tags Tab Report Tab Rule Configuration Tab Administration Tab Optimizer Tab Cost Tab Policy Management Tab

Editing agent properties

AWS Agents collect data from your AWS infrastructure and send it to the Management Server. The agents keep track of resource utilization metrics and alerts you when certain pre-defined thresholds are reached.

Default versions of these properties are installed with Foglight. However, you can edit the default agent properties, configure the agent properties that apply only to a specific agent instance, and create edited clones of shareable properties that are used by a subset of certain agent type.

To edit the AWS Performance Agent properties:
1
Log in to the Foglight browser interface.
2
Ensure that the navigation panel is open.
To open the navigation panel, click the right-facing arrow on the left.
3
On the navigation panel, under Homes, click Cloud Manager.
Cloud Manager dashboard opens.
4
Click Administration.
The Administration dashboard opens.
5
Select the instance of the AWS Agent properties that you want to modify, and then click Edit Properties.
6
In the Edit Properties dialog box, edit the following properties, as needed.
•
Account Alias: The display name of this account.
•
Access Key ID: The access key retrieved in Getting authentication information through console .
•
Secret Access Key: The secret access key retrieved in Getting authentication information through console .
•
Collect Memory Metric: Select this option to enable the collection of instance memory metrics. The default value is disabled.
•
Collect Linux Volume Utilization: Select this option to enable the collection of Linux volume utilization. The default value is disabled.
•
Specify an agent name (Optional): Specify the name of agent.
•
Configure regions to be monitored (Optional): Select AWS regions for monitoring. All regions will be monitored if this field is not configured.
•
Select Virtual Machines to Monitor: Specify to monitor all virtual machines or only monitor specified instance.
•
If Monitor All is selected: By monitoring all virtual machines any virtual machine that is running in the monitored cloud will be monitored 24x7 consuming a monitored virtual machine license. Every virtual machine that is monitored will count against the purchased license pool. Any Monitored Virtual Machine that is above the purchased license limit will require an additional Foglight Hybrid Cloud Manager per Monitored Virtual Machine license.
•
If Monitor All is not selected: The following view appears on the bottom of the Selected IaaS Virtual Machines to Monitor dialog box.
•
If Automatically Monitor New Instances is selected, select instances that you do not want to monitor, and then click >> to move selected instances to the Removed from Monitoring table.
•
If Automatically Monitor New Instances is not selected, select instances that you want to monitor, and then click >> to move selected instances to the Virtual Machines Monitored by Foglight Hybrid Cloud Manager table.
•
If the Removed from Monitoring and Virtual Machines Monitored by Foglight Hybrid Cloud Manager tables are empty, and Automatically Monitor New Instances is not selected, the AWS agent will not collect any instance data.
•
Configure Account Cost to Monitor:
Configure the Cost Metrics collection. Collections will start only after the AWS Cost and Usage Report are created on the AWS Console. See To create an AWS Cost and Usage Report.
•
Collect Cost Metrics: Select the check box to enable and configure the cost metrics collection. Collections will start only after the AWS Cost and Usage Report are created on the AWS Console. See To create an AWS Cost and Usage Report.
•
Configure Monitor Account: Click Configure to select the accounts for which costs should be monitored.
By default, Collect All Account Cost is selected. This will collect consolidated billing information for all accounts in a single organization. To manually select accounts for cost collection, clear Collect All Account Cost.
•
Select Account: When Collect All Account Cost is cleared, a list of AWS accounts in your organization will be displayed. Note that accounts will only be displayed after a successful data collection. In the AWS Account table, select the accounts to monitor and click to add the accounts to the Target AWS account table.
Adding accounts: If the desired accounts do not appear in the accounts listed in the AWS Account table, you can manually add the account by clicking Add and supplying the Account ID (See To get Account ID (12-digit number) to get this value) and Account Name.
Note: Accounts added to the AWS Account table will not be saved unless they are moved to the Target AWS table.
•
Import/Export accounts: In addition to manually adding accounts, they can be imported (from a CSV file) to either the AWS Account or Target AWS Account table. Accounts can also be exported from the Target AWS Account table.
The CSV file should contain two columns :Account ID(12-bit Numbers) and Account Alias Name. See To get Account ID (12-digit number) for more information.
Note: Accounts imported to the AWS Account table will not be saved unless they are moved to the Target AWS table.
•
Click Save to save changes.
•
S3 Bucket for Cost and Usage Report: Enter the name of your S3 bucket according to the AWS Cost and Usage Report setting. See To create an AWS Cost and Usage Report to get this value.
•
S3 Bucket Region for Cost and Usage Report: Select the region of your S3 bucket according to the AWS Cost and Usage Report setting. See To create an AWS Cost and Usage Report to get this value.
•
Cost and Usage Report Name: Enter the name of your AWS Cost and Usage report. See To create an AWS Cost and Usage Report to get this value.
•
Cost and Usage Report Path: Enter the Report path prefix according to your Report setting. The value of Cost and Usage Report Path will be blank, if you don't set the Report path prefix in AWS. See To create an AWS Cost and Usage Report to get this value.
•
Configure Proxy (Optional):
Configure the proxy setting when the Agent Host requires a proxy connection to the Internet.
a
Select the Enable Proxy check box to enable the proxy settings.
b
Input the host name or IP address for the Proxy Server and input the Proxy Port number.
c
If the proxy requires an authorization, select the Authorization check box, and input the Username and Password.
* 
NOTE: In FIPS-compliant mode, if proxy settings are configured, you need to import the proxy server application root certificate into FMS KeyStore and FgLAM. For more information, see Managing certificates.
7
Click Save. The Edit Properties dialog box closes and the list of agent instances automatically refreshes in the display area.

Managing certificates

Syntax Conventions

In order to successfully make use of the Foglight commands in your monitoring environment, review the syntax conventions before getting started. The syntax conventions are as follows:

•
Generic examples follow the UNIX path structure that uses forward slashes '/' to separate directories.
•
Platform-specific examples follow standard platform conventions. For example, UNIX-specific examples use forward slashes ‘/’ as directory delimiters, while Windows examples use backslashes ‘\’.
•
<foglight_home> is a placeholder that represents the path to the Foglight Management Server installation.
•
<foglight_agent_mgr_home> is a placeholder that represents the path to the Foglight Agent Manager installation. This can be the location of the Foglight Agent Manager installation on a monitored host, or the home directory of the Foglight Agent Manager that comes embedded with the Foglight Management Server. For example:
Path to the Foglight Agent Manager installation on a monitored host (Windows):
C:\Quest\Foglight_Agent_Manager
Path to the embedded Foglight Agent Manager installation (Windows):
C:\Quest\Foglight\fglam
•
Unless otherwise specified, Foglight commands are case-sensitive.

Syntax Conventions

Managing certificates

In order to successfully make use of the Foglight commands in your monitoring environment, review the syntax conventions before getting started. The syntax conventions are as follows:

•
Generic examples follow the UNIX path structure that uses forward slashes '/' to separate directories.
•
Platform-specific examples follow standard platform conventions. For example, UNIX-specific examples use forward slashes ‘/’ as directory delimiters, while Windows examples use backslashes ‘\’.
•
<foglight_home> is a placeholder that represents the path to the Foglight Management Server installation.
•
<foglight_agent_mgr_home> is a placeholder that represents the path to the Foglight Agent Manager installation. This can be the location of the Foglight Agent Manager installation on a monitored host, or the home directory of the Foglight Agent Manager that comes embedded with the Foglight Management Server. For example:
Path to the Foglight Agent Manager installation on a monitored host (Windows):
C:\Quest\Foglight_Agent_Manager
Path to the embedded Foglight Agent Manager installation (Windows):
C:\Quest\Foglight\fglam
•
Unless otherwise specified, Foglight commands are case-sensitive.

Managing certificates for FglAM

Foglight Evolve agents use Foglight Agent Manager (FglAM) to manage certificates for SSL encryption connection.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating