Comments on: SCOM: WSH Vs. PowerShell Modules in Composite Workflows – Resource Utilization in SNMP Data Manipulation http://operatingquadrant.com/2009/10/03/scom-wsh-vs-powershell-modules-in-composite-workflows-resource-utilization-in-snmp-data-manipulation/ Living in the I.T. Operating Quadrant. Useful articles on real world solutions involving Monitoring (System Center Operations Manager), Virtualization, Reporting, Scripting (PowerShell), and much more. Tue, 31 Jan 2012 01:50:45 +0000 hourly 1 http://wordpress.com/ By: Scalability and Performance Design and Testing in the xSNMP Management Packs « Operating-Quadrant http://operatingquadrant.com/2009/10/03/scom-wsh-vs-powershell-modules-in-composite-workflows-resource-utilization-in-snmp-data-manipulation/#comment-352 Tue, 15 Dec 2009 01:39:13 +0000 http://operatingquadrant.com/?p=274#comment-352 [...] SCOM: WSH Vs. PowerShell Modules in Composite Workflows – Resource Utilization in SNMP Data&nb… [...]

]]> By: SCOM: Distributing Workflows with the SpreadInitializationOverInterval Scheduler Parameter « Operating-Quadrant http://operatingquadrant.com/2009/10/03/scom-wsh-vs-powershell-modules-in-composite-workflows-resource-utilization-in-snmp-data-manipulation/#comment-234 Tue, 13 Oct 2009 01:28:01 +0000 http://operatingquadrant.com/?p=274#comment-234 [...] SCOM: WSH Vs. PowerShell Modules in Composite Workflows – Resource Utilization in SNMP Data&nb… [...]

]]> By: Kristopher Bash http://operatingquadrant.com/2009/10/03/scom-wsh-vs-powershell-modules-in-composite-workflows-resource-utilization-in-snmp-data-manipulation/#comment-231 Sat, 10 Oct 2009 15:25:05 +0000 http://operatingquadrant.com/?p=274#comment-231 Cookdown requires that all inputs to the workflow be identical. Using network interface objects as an example, cookdown is viable for a single interface, but not multiple interfaces because their index values(used to define the OID to poll with the SNMP Get) will differ. Using a workflow that collects interface octet counts which are passed to a PowerShell script to calculate % utilization and Mbit throughput, multiple performance collection rules (% in utilization, % out utilization, Mbit In, Mbit Out) and monitors can utilize the same datasource and cookdown for a single interface object, as long as the input parameters (schedule interval, interface index, device IP address, etc) are identical.

I’m currently expirementing with means to randomly spread scheduled workflows out over time to prevent all scheduled workflows with the same interval from hitting at once. I’m also trying to eliminate script probes wherever possible and replace them with either simple SNMP probes if viable and in at least one case, mapping the SnmpData to PerformanceData in order to utilize the Performance Delta Value module to calculate the Delta. It’s a work in progress though.

]]> By: Dan Nichols http://operatingquadrant.com/2009/10/03/scom-wsh-vs-powershell-modules-in-composite-workflows-resource-utilization-in-snmp-data-manipulation/#comment-229 Sat, 10 Oct 2009 12:34:09 +0000 http://operatingquadrant.com/?p=274#comment-229 Hi Kris,

I presume that cookdown of the cscript processes is not possible with your multi-module composite data source?

K.Regards,

Dan.

]]>