Monitoring is not just "reviewing logs". Sometimes it is necessary to acquire performance information, which then goes into a database and forms the basis for creating reports, sometimes also charts placed, for example, in the visualization of some process.
When some performance counter is not collected by Operations Manager the matter seems simple (and usually is): we check with the tool Performance Monitor what the object and counter are called, what the counter instances look like, and then you can construct a performance collection rule (Performance Collection Rule).
When the need arose to collect the value of the counter "Batch Requests/sec", after applying the MP Author tool, the following configuration of the collection rule data source was created
The result of applying the gathering rule was disappointing, although in the lab setup "everything works". Data from named instances did not appear at all.
It is only when you look at the model Management Pack, designed to monitor SQL 2005-2012, that you can see that it is necessary to make the object name different, and the attribute is responsible for this. PerformanceCounterObject
After such a fix, the rule also "took off" for named instances and the awaited charts appeared:
Thus, "missing" instances are also shown in the chart. It is worth noting that Performance Monitor also reveals the corresponding object names, it only needs to be "opened" the network path, not the local computer (because then the default instance is shown).
