Chat now with support
Chat with Support

Foglight Agent Manager 5.9.3 - Foglight Agent Manager Guide

Configuring the embedded Agent Manager Installing external Agent Managers
Understanding how the Agent Manager communicates with the Management Server Deploying the Agent Manager cartridge Downloading the Agent Manager installer Installing the Agent Manager Starting or stopping the Agent Manager process Frequently asked questions
Configuring the Agent Manager Advanced system configuration and troubleshooting
Configuring Windows Management Instrumentation (WMI) Configuring Windows Remote Management (WinRM) UNIX- and Linux-specific configuration
Monitoring the Agent Manager performance Deploying the Agent Manager to large-scale environments

Adding cartridges to the HA deployment whitelist

In addition to assigning an Agent Manager to an HA Partition, real HA activities do not take place until HA Aware agent types are deployed.

To provide eligibility for HA agent fail-over to existing agents that primarily function as remote monitors, the HA Deployment Whitelist property is included. This list-based property identifies prior cartridge deployments that were not originally marked as eligible for HA agent fail-over. In this list, each row entry contains a regular expression pattern that matches the agent package, version and agent types that are permitted to be managed in an HA Partition.

Understanding the criteria for HA eligibility

The criteria for inclusion into this list is that the agent type must be capable of monitoring remote resources. It does not make sense to enable HA fail-over for an agent that is collecting data that can only be retrieved from the Agent Manager host on which it is running. If such an agent is added to the Whitelist, when the host fails over, the agent can potentially start monitoring the resources of the newly promoted HA Primary, which can result in unexpected outcome when viewing the dashboards that display the collected metrics.

 
* 
IMPORTANT: To effectively be eligible for fail-over functionality, agents must be using one of the RemoteConnection Services available in the Agent Manager Development Kit.
To add an entry to the Whitelist:
1
Ensure that the Agent Manager is connected to the Management Server.
2
Log in to the Foglight browser interface.
3
On the navigation panel, under Dashboards, navigate to Administration > Agents > Agent Properties.
4
On the Agent Properties dashboard that appears in the display area, in the Namespace/Type view, expand the FglAM node, and click the FglAMAdapter node.
5
Add a new regular expression to select a desired agent type and add it to the Whitelist.
a
Get started with editing the HA Deployment Whitelist property.
In the Properties view, under High Availability, on the right of the HA Deployment Whitelist property, click Edit.
b
Add a new regular expression to the table.
In the dialog box that appears, click Add Row, and in the new row that appears, type a regular expression using the following syntax:
[Agent_package]/[Agent_version]/[Agent_type
 
* 
IMPORTANT: The elements in the expression must be separated with slashes ‘/’.
c
Click Save Changes.
6
If the cartridge containing the specified agent type is not already installed, install it using the Cartridge Inventory dashboard, and deploy its agent package to an Agent Manager that is assigned to an HA partition.

About agent fail-over

When the HA Primary host goes off-line, a schedule is registered that delays the transfer of the agents (and the promotion of another HA Primary) for two minutes. This delay is in place to allow the HA Primary host to be restarted and retain its HA status and assigned agents. If you find that the duration is too long, the following startup parameter can be set when launching the Management Server:

-Dfglam.ha.agent.transfer.delay.milliseconds=XXXX

About non-HA deployments

Agent Managers that are assigned to an HA Partition can still manage deployments and agents that are not HA Aware. When these cartridges are deployed to an Agent Manager, they by-pass the HA Deployment Set checks and are only deployed to this host. If this host goes offline, any non-HA agents also become off-line.

Negotiating Agent Manager resources at runtime

Monitoring agents often have specific Agent Manager resource requirements. Some agents need more memory, others require larger queue sizes, or more lenient time-outs. The Agent Negotiation feature allows monitoring agents to request resource changes during deployment, activation, and runtime. During deployment, an agent package can request specific resource settings to applied as part of the deployment process. Depending on the current Agent Manager configuration, a restart may be required in order to apply the requested changes. This restart of the Agent Manager is automatic and is part of the deployment cycle.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating