Chat now with support
Chat mit Support

Foglight Agent Manager 5.9.1 - 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

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.

Disabling runtime resource negotiation

Disabling runtime resource negotiation causes the Agent Manager to revert to running under its default startup configuration.

To disable runtime resource negotiation on startup:
•
Set up the following runtime switch on the command line:
./fglam --disable-overrides
To permanently disable runtime resource configuration:
1
If the Agent Manager process is running, shut it down.
2
Edit the <FGLAM_STATE>/config/client.config file to include the following block of code:
# *** Disable Deployment Overrides ***
#
# Set this value to true in order to disable the resource settings
# negotiation from occurring when an AgentPackage is deployed.
disable.overrides = true;
3
Save the changes.
4
Start the Agent Manager.

Disabling agent-specific changes to the upstream queue

The config/fglam-config.xml file contains an attribute that allows you to disable any agent-specific changes to the upstream queue settings at runtime. By default this attribute is set to true. You can use this feature, for example, to prevent individual agents to negotiate allocating large amounts of memory.

<config:upstream max-queue-size="-1" max-disk-space="1024" max-batch-size="500"
allow-runtime-change="false"/>
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen