Process Monitoring policy impact.
Article ID: CTX558874
Updated On:
Description
Understand impact of Process Monitoring policy.
Instructions
1) Use cases and best practices on using the Process Monitoring policy settings
Process Monitoring is for troubleshooting use cases, if you see CPU/Memory being high on a few machines or
a DG and want to know what's causing that, enable Process Monitoring on those machines or DG.
Disable the policy once the use case is troubleshooted.
2) The length of time the data will be kept and how often it's cleaned
Raw data is retained for 24 hours and is aggregated to hourly and monthly rollups.
The raw data is cleaned every 4 hours and aggregated data is cleaned as per the retention policies.
3) Whether any cost is involved, as the SQL is hosted by Citrix
In cloud, the cost is with Citrix DaaS, in cloud, Citrix DaaS service hosts and maintains the SQL database and the cost is included in the DaaS service licence.
4) Whether any significant impact on networking, Cloud Connectors, VDA is expected
No
Concern is not just with the cloud connector, but also about VDA performance impact.
One aspect: if to enable process monitoring and resource monitoring from Citrix policies,
does the monitoring service use large amount of VDA resources (CPU, Memory, Network, Disk IO) to gather this data which
would ultimately impact user experience ?
There should be no impact to end user experience.
Issue/Introduction
Understand impact of Process Monitoring policy.
Was this article helpful?
Yes
No
Powered by
