Assign a user account to the Role
Assign a user account to the RoleTo assign a user account to a Role:In the VMware Virtual Infrastructure Client, on the toolbar, click Inventory.The Inventory screen appears.In the left pane, right-click Hosts & Clusters, and select the root item in the tree, the Virtual Center object.Right click and select Add Permission.In the Assign Permissions dialog box, in the Assigned Role area, select the role you just created.Ensure that the Propagate to Child Objects check box is selected.In the Users and Groups area, click Add.The Select Users dialog box appears.Assign the selected role to a user account that will be configured for monitoring (user account that you want the VMware Performance Agent to use for accessing the Virtual Center), and click Add.Click OK.The Select Users dialog box closes.When creating the VMware Performance agent, use the user account assigned to the new Role.
Enable optional privileges for resource optimization
Enable optional privileges for resource optimizationTo enable automated resource optimization, the service account requires additional privileges. The following permissions should be added to the Role you just created.
Credentials required for optimization
Foglight Resource Optimizer provides recommendations for changes in the VMware® environment to make more efficient use of resources. As a prerequisite, a VMware agent must be configured with a user that has elevated privileges, beyond the read-only privileges required for monitoring.For a list of privileges required for the VMware agent, see section “Configuring Monitoring Agents for Data Collection” in the Foglight for VMware User and Reference Guide.Credentials groups for resource optimization can be defined using the Credentials tab.
The Optimizer dashboard automatically displays the virtual machine hosts (VMware® target machines) that Foglight or Foglight for Virtualization, Enterprise Edition monitors, for which resource optimization recommendations are provided. No further setup is required.
Each Federated Child should be configured to monitor its own unique environment. There should be no overlap between the monitored environments, such that no two Federated Children are monitoring the same nodes (VM, Server, Datastore, etc.). Incorrect configuration results in topology churn on the Foglight Federation Master.