-
-
-
-
-
-
Querying Windows Performance Counters
-
Building a Browser Extension Inventory Report (Chrome/Edge/Firefox)
-
Internet Explorer - Distinguish Standalone and Edge IE Mode Starts
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!
Querying Windows Performance Counters
In addition to its built-in metrics, uberAgent can collect data from Windows performance counters.
Configuration
As with all other uberAgent metrics, performance counters need to be associated with a timer that defines how often data is collected. Performance counter metrics can be added to an existing timer or placed in a new timer section. See the configuration docs and the performance counter metrics documentation for details.
Example
In the following example, we configured a new timer that collects data every 60 seconds. We added two performance counters to the timer that collect .NET information for the entire machine and for a specific process (PowerShell). We also added a performance counter that collects the system’s uptime. Finally, we added a performance counter that collects the handle count for every running process. The result looks like this:
[Timer]
Name = Performance counter timer
Interval = 60000
Perf counter = \.NET CLR Memory(_Global_)\# Gen 0 Collections
Perf counter = \.NET CLR Memory(powershell)\# Gen 0 Collections
Perf counter = \System\System Up Time
Perf counter = \Process(*)\Handle Count
<!--NeedCopy-->
Counter Paths
Most performance counter paths have one of the following two formats:
\object(instance)\counter
\object\counter
<!--NeedCopy-->
As you can see, some counter paths have instance names (powershell
in one of the examples above) while others do not.
See Microsoft Docs for more information.
Wildcards
uberAgent can use the wildcard characters *
and ?
in the instance section of performance counter paths.
Finding Counter Paths
To find the paths for your counters you can use the following method.
Add the desired counters to Performance Monitor. Then right-click the graph section of Perfmon’s window, select Save settings as..., save as web page (*.html
) and locate the counter path in the HTML code. Perfmon saves the counter path in language-neutral format, which is what is uberAgent needs.
Language-Neutral or Localized
Some tools require localized performance counter paths. This becomes a problem if you configure paths for machines with different language versions of Windows.
With uberAgent, you can configure localized or language-neutral performance counter paths. The performance counter path is always sent to the backend in English.
Share
Share
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.