-
-
-
-
-
-
-
Citrix Applications Are Still Displayed with Old Name After Renaming
-
Differences between SessionPublishedAppsCtx and SessionPublishedName
-
How to Configure the Data Collection Frequency
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
How to Configure the Data Collection Frequency
By default, uberAgent collects performance data every 30 seconds. This interval can be changed in the configuration.
Timers
uberAgent can run an unlimited number of independent timers. Each timer wakes up at regular intervals and collects the metrics assigned to it. When a timer has completed a data collection task, it goes back to sleep for the configured length of the timer interval. This means that the time between data collections is the length of the timer interval plus the time it takes to collect the data.
Timer Runtime
In most cases data collection is nearly instantaneous and, therefore, the time between data collections is essentially identical to the timer interval. In some rare cases, e.g., where data is collected from WMI, the data collection may take a noticeable amount of time. In such cases, the time between data collections may be significantly longer than the configured timer interval.
Note: uberAgent’s timers do not guarantee a certain number of data collections per time unit. Do not assume that, for example, a 30 second timer interval yields exactly two events per minute.
Changing the Timer Interval
As mentioned above, data collection happens every 30 seconds by default for most metrics. To change the interval to, e.g., 10 seconds, edit the uberAgent.conf
configuration file so that the lines where the intervals are configured read like this:
# interval unit: milliseconds
interval = 10000
If, on the other hand, you want to receive only certain metrics at a higher resolution (e.g. 5 seconds), create a new timer section as follows:
[Timer]
Name = High-frequency GPU usage
Comment = Isolate GPU metrics from the other metrics
# interval unit: milliseconds
Interval = 5000
UA metric = GpuUsage
With this configuration, uberAgent collects GPU usage data every five seconds. Be sure to remove the GPUUsage
metric from any other timers, or it will be collected there as well.
In addition to timers that collect data at time-based intervals, uberAgent also has on-demand metrics that collect data when specific events occur, such as user logins.
Note: Be sure to consider metric dependencies when separating metrics and placing them in individual timers.
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.