Setting Agent Properties
The EdgeSight Agent stores configuration data in two locations. The Windows registry on the managed device is used to store configuration items which are machine specific and are required for successful communication with the EdgeSight Server. For example, the name of the company the agent belongs to, the name of the server to contact, and any proxy information required to perform the communication are all stored in the registry. All other configuration items are stored in the EdgeSight Agent database.When the agent is running on virtual desktops in a pooled environment, the agent database is located on a remote server.
The items stored in the Windows registry are typically set once, and are supplied during agent installation. All other configuration items are supplied by the associated EdgeSight Server, and any changes in configuration are performed using the Agent Properties page. By default, an agent obtains its initial configuration shortly after the agent first runs and then queries for configuration changes. The default schedule for configuration checks is set to 6:30 AM agent local time every day for endpoint devices and every hour for XenApp servers. Agents running on virtual desktops in a pooled environment will perform configuration checks based on actual usage.
Care should be taken when changing agent properties. These parameters control the way the agent works and could result in users perceiving data loss or an increased CPU usage by the agent. In most cases, you will not need to customize agent properties. Use the default configuration at first and adjust it over time based on user requirements and system performance.
Agent property configurations are displayed on the Agent Properties page (). When creating a new set of agent properties, you must choose a default configuration (Endpoints Default, XenApp Default, or Virtual Desktop Default) to use as a template. Provide a unique configuration name and description, and edit the parameters as required.
Once a custom set of agent properties has been created, it must be explicitly mapped to a department before it is provided to agents as part of a configuration check. (See “Managing Departments” in Managing Departments, Devices, and Groups for information on associating a set of agent properties with a department.)
For information on the individual parameters that make up agent properties, see the “Agent Properties Wizard” topic in online help.
Minimal Data Collection Mode
In order to support busy XenApp server environments, the EdgeSight agent has a Minimal Data Collection Mode feature that, when enabled, limits the data collected on the agent and thus the overall impact the agent has on the XenApp server.
When a XenApp server is consistently experiencing heavy load, or the XenApp server slows considerably under load, it is time to consider using this feature. Use EdgeSight reports to note the number of sessions and processes at which a considerable slow down occurs. These numbers are used to establish when Minimal Data Collection Mode is initiated on the agent.
The Minimal Data Collection Mode is disabled by default. To enable it, edit the agent properties and display the advanced settings. Set Manage Data Collection to True and enter values that you collected in the Process Count Threshold and Session Count Threshold fields. Then assign this set of agent properties to the XenApp server experiencing the problem.
When Minimal Data Collection Mode is enabled, the agent periodically monitors the process and session counts against the configured thresholds. If either threshold exceeds its specified value, the agent enters Minimal Data Collection Mode. At this point an operational alert is sent to the server, “The Citrix System Monitoring Agent has entered Minimal Data Collection Mode.” When both process and session counts return below the threshold settings for 5 minutes, the agent will leave Minimal Data Collection Mode and normal data collection will be resumed. A bullet is sent to the server to indicate that the agent has left Minimal Data Collection Mode.
Minimal Data Collection differs from normal data collection in the following ways:
- No module data is collected or persisted
- No network data is collected or persisted
- No light trace events are persisted
- No image or principal events are persisted (currently not visible)
- No task details used in fault reports will be persisted
- Hung application detection is disabled
- Image and session performance data is persisted at a 2 minute granularity
- Custom performance counter collection is disabled
- Performance, network, and event trace alerts are disabled
Other configuration changes that exist on EdgeSight for XenApp include:
System, image, and session performance fine grain data is persisted at 15 second intervals.
If the scheduler detects more than 5 concurrent sessions running, it will not use idleness to gate when scheduled items such as consolidation can run. Instead the assumption is made that this is a server system and therefore there may never be best idle moments for schedules to run.
Individual workers can be configured on the server to similarly ignore idleness when making a determination for a best time to run.