Shulou(Shulou.com)06/02 Report--

This article shows you how to analyze Multiple Property Bags in the development of SCOM management packs. The content is concise and easy to understand. It will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

The previous article talked about how to save time, and in workflow composite in Authoring guide, it's best to have scripts support Cookdown. Then my script returns multiple Property bags.

To support cookdown, I designed a custom datasource, defined as follows, simply execute the powershell script mentioned in the previous article periodically, this script outputs multiple Property bags, in order to reuse module, I added a conditionDetection and used regular expressions to filter property bag, so that you can monitor different attribute values by simply filtering specific attributes.

Let's go straight to the picture. DS definition

Here is the Monitor configuration. Given the design of the above DS, I can use Snippet Template in VSAE to generate multiple Monitor very quickly.

My Monitor type definition

Snippet Data

One of the XML codes for the generated Monitor.

In fact, the above DS design using MatchedWildCard can use wildcard matching with another selfish. Because I know that System.Performance.DataGenericMapper supports the conversion of multiple Property Bags to multiple Performance data at one time, if my Datasource enters * when comparing attributes, then it returns the values of all monitored properties, and then all of them are converted to perf data through a System.Performance.DataGenericMapper, and then a rule can be directly written to DB,DWDB. The idea is good, the code can be compiled, and there is no error after importing MP.

But when I use performance widget, I only see an option for a performance counter. I have eight counters.

I checked the search engine and said that the data used by perf Widget is in DWDB. I'll see if there is any data.

When performance data is written to DWDB, the CounterName is all the same, but the Value is correct. I searched with the keyword Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData batching and found the following link.

The pit remains the same for many years.

Http://www.systemcentercentral.com/forums-archive/topic/multi-value-rule-data-not-published-to-data-warehouse/

The perf view data in SCOM Console uses data from OperationMangerDB, while Perf Widget uses data from OperationmangerDWDB. Microsoft.SystemCenter.CollectPerformanceData supports writing multiple perf data at once when writing to OperationMangerDB, while Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData does not support writing to OperationmangerDWDB.

My original rule is written like this, so it looks like it's going to be broken into multiple pieces.

Fortunately, DS was better designed at that time, so dismantling was not a problem. It can be done quickly with snippet template.

This quickly generates eight Rule.

The above content is how to analyze Multiple Property Bags in the development of SCOM management package. have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.