Windows Performance Counters - Revision history

AlexKirhenshtein: Text replacement - "^" to "{{deprecated}}"

2022-09-13T16:14:04Z

Text replacement - "^" to "{{deprecated}}"

← Older revision		Revision as of 16:14, 13 September 2022
Line 1:		Line 1:
	{{DISPLAYTITLE:Introduction}}		{{deprecated}}{{DISPLAYTITLE:Introduction}}
	NetXMS allows the collection of DCI from several origins. The Windows Performance Counters origin is a particular origin that can be used to monitor the performance counters exposed on a specific node.<br />		NetXMS allows the collection of DCI from several origins. The Windows Performance Counters origin is a particular origin that can be used to monitor the performance counters exposed on a specific node.<br />
	Currently this origin is available only for the Windows agent starting from version 1.2.7.<br />		Currently this origin is available only for the Windows agent starting from version 1.2.7.<br />

Macro: /* DCI computed exporting it form the Agent configuration file */

2013-04-02T09:06:11Z

DCI computed exporting it form the Agent configuration file

← Older revision		Revision as of 09:06, 2 April 2013
Line 20:		Line 20:
	<br />		<br />
	== DCI computed exporting it form the Agent configuration file ==		== DCI computed exporting it form the Agent configuration file ==
	~~As first step~~, it is necessary to edit the agent configuration file to export the ~~interested~~ counter. Adding these lines and restarting the agent will do the job:		First, it is necessary to edit the agent configuration file to export the counter of interest. Adding these lines and restarting the agent will do the job:

	*WinPerf		*WinPerf

Victor: /* DCI computed exporting it form the Agent configuration file */

2013-04-02T05:28:10Z

DCI computed exporting it form the Agent configuration file

← Older revision		Revision as of 05:28, 2 April 2013
Line 20:		Line 20:
	<br />		<br />
	== DCI computed exporting it form the Agent configuration file ==		== DCI computed exporting it form the Agent configuration file ==
	As first step, it is necessary to edit the agent configuration file to export the interested counter. Adding these lines and restarting the agent will do the job:~~<br />~~		As first step, it is necessary to edit the agent configuration file to export the interested counter. Adding these lines and restarting the agent will do the job:
	~~<br />~~
	''*WinPerf~~''<br />~~		*WinPerf
	''Counter = Hyper-V Hypervisor Virtual Processor.%Total Run Time(_Total):"\Hyper-V Hypervisor Virtual Processor(_Total)\% Total Run Time":60:A:INT:"The percentage of CPU used by Hyper-V Guests."~~''<br />~~		Counter = Hyper-V Hypervisor Virtual Processor.%Total Run Time(_Total):"\Hyper-V Hypervisor Virtual Processor(_Total)\% Total Run Time":60:A:INT:"The percentage of CPU used by Hyper-V Guests."
	~~<br />~~
	Then, it is possible to select it from the Agent:<br />		Then, it is possible to select it from the Agent:<br />
	<br />		<br />
	[[File:origin_agent.png]]		[[File:origin_agent.png]]

Marco Incalcaterra at 18:14, 1 April 2013

2013-04-01T18:14:33Z

← Older revision		Revision as of 18:14, 1 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:Introduction}}		{{DISPLAYTITLE:Introduction}}
			NetXMS allows the collection of DCI from several origins. The Windows Performance Counters origin is a particular origin that can be used to monitor the performance counters exposed on a specific node.<br />
			Currently this origin is available only for the Windows agent starting from version 1.2.7.<br />
	= Windows Performance Counters =		= Windows Performance Counters =
			After choosing the Windows Performance Counters as origin, pressing the select button will pop up the hierarchy tree from where to select the interested counter:<br />
	NetXMS allows the collection of DCI from several origins. The Windows Performance Counters origin is a particular origin that can be used to monitor the performance counters exposed on a specific node. Currently this origin is available only for the Windows agent starting from version 1.2.7.		<br />

	After choosing the Windows Performance Counters as origin, pressing the select button will pop up the hierarchy tree from where to select the interested counter:

	[[File:list_wpc.png]]		[[File:list_wpc.png]]
			<br />
	The left side of the dialog lists all the counters available, whether the right side of the dialog lists all the instances available for the selected counter.		<br />
			The left side of the dialog lists all the counters available, whether the right side of the dialog lists all the instances available for the selected counter.<br />
	The main difference between the performance counters ~~selected here~~ and the performance counters ~~exposed by agent configuration~~ is the major flexibility of this approach:		The main difference between the performance counters exposed by agent configuration and the performance counters selected here is the major flexibility of this new approach:<br />

	* This DCI can be easily transformed in template and applied to new nodes without any kind of interaction with the configuration file.		* This DCI can be easily transformed in template and applied to new nodes without any kind of interaction with the configuration file.
	* The value can be used “as it is” or can be generated as an average between a group of samples, at agent level. The number of sample used to compute the average must be put in the “Sample value for average value calculation” field (NB high number of sample will delay the computation of the initial value).		* The value can be used “as it is” or can be generated as an average between a group of samples, at agent level. The number of sample used to compute the average must be put in the “Sample value for average value calculation” field (NB high number of sample will delay the computation of the initial value).<br />
			All the other configuration values such as Polling (mode and interval) or Storage (retention time) have the same logic used for other origins. It is important to note that average computation will be done at agent level, thus reducing network traffic and DB storage resources.<br />
	All the other configuration values such as Polling (mode and interval) or Storage (retention time) have the same logic used for other origins. It is important to note that average computation will be done at agent level, thus reducing network traffic and DB storage resources.		Here follows an example of the CPU resource usage by Hyper-V guests computed using the Windows Performance Counters origin vs Agent origin.<br />

	Here follows an example of the CPU resource usage by Hyper-V guests computed using the Windows Performance Counters origin vs Agent origin.

	== DCI computed using the Windows Performance Counters origin ==		== DCI computed using the Windows Performance Counters origin ==
			As sole step, it is necessary to select it from the list of available counters:<br />
	As sole step it is necessary to select it from the list of available counters:		<br />

	[[File:origin_wpc.png]]		[[File:origin_wpc.png]]
			<br />
	== DCI computed exporting it form the Agent configuration file ==		== DCI computed exporting it form the Agent configuration file ==
			As first step, it is necessary to edit the agent configuration file to export the interested counter. Adding these lines and restarting the agent will do the job:<br />
	As first step it is necessary to edit the agent configuration file to export the interested counter ~~adding~~ these lines and restarting the agent:		<br />

	''*WinPerf''<br />		''*WinPerf''<br />
	''Counter = Hyper-V Hypervisor Virtual Processor.%Total Run Time(_Total):"\Hyper-V Hypervisor Virtual Processor(_Total)\% Total Run Time":60:A:INT:"The percentage of CPU used by Hyper-V Guests."''		''Counter = Hyper-V Hypervisor Virtual Processor.%Total Run Time(_Total):"\Hyper-V Hypervisor Virtual Processor(_Total)\% Total Run Time":60:A:INT:"The percentage of CPU used by Hyper-V Guests."''<br />
			<br />
	Then, it is possible to select it from the Agent:		Then, it is possible to select it from the Agent:<br />
			<br />
	[[File:origin_agent.png]]		[[File:origin_agent.png]]

Marco Incalcaterra: Created page with "{{DISPLAYTITLE:Introduction}} = Windows Performance Counters = NetXMS allows the collection of DCI from several origins. The Windows Performance Counters origin is a particul..."

2013-04-01T16:45:51Z

Created page with "{{DISPLAYTITLE:Introduction}} = Windows Performance Counters = NetXMS allows the collection of DCI from several origins. The Windows Performance Counters origin is a particul..."

New page

{{DISPLAYTITLE:Introduction}}
= Windows Performance Counters =

NetXMS allows the collection of DCI from several origins. The Windows Performance Counters origin is a particular origin that can be used to monitor the performance counters exposed on a specific node. Currently this origin is available only for the Windows agent starting from version 1.2.7.

After choosing the Windows Performance Counters as origin, pressing the select button will pop up the hierarchy tree from where to select the interested counter:

[[File:list_wpc.png]]

The left side of the dialog lists all the counters available, whether the right side of the dialog lists all the instances available for the selected counter.

The main difference between the performance counters selected here and the performance counters exposed by agent configuration is the major flexibility of this approach:

* This DCI can be easily transformed in template and applied to new nodes without any kind of interaction with the configuration file.
* The value can be used “as it is” or can be generated as an average between a group of samples, at agent level. The number of sample used to compute the average must be put in the “Sample value for average value calculation” field (NB high number of sample will delay the computation of the initial value).

All the other configuration values such as Polling (mode and interval) or Storage (retention time) have the same logic used for other origins. It is important to note that average computation will be done at agent level, thus reducing network traffic and DB storage resources.

Here follows an example of the CPU resource usage by Hyper-V guests computed using the Windows Performance Counters origin vs Agent origin.

== DCI computed using the Windows Performance Counters origin ==

As sole step it is necessary to select it from the list of available counters:

[[File:origin_wpc.png]]

== DCI computed exporting it form the Agent configuration file ==

As first step it is necessary to edit the agent configuration file to export the interested counter adding these lines and restarting the agent:

''*WinPerf''<br />
''Counter = Hyper-V Hypervisor Virtual Processor.%Total Run Time(_Total):"\Hyper-V Hypervisor Virtual Processor(_Total)\% Total Run Time":60:A:INT:"The percentage of CPU used by Hyper-V Guests."''

Then, it is possible to select it from the Agent:

[[File:origin_agent.png]]