When creating a set of dashboards for different servers in our environment, we started with the creation of a group which had the servers defined within it. Once this was done, we create a series of views to show us the state of the servers and to show relevant performance information. The user requirement was a single performance view that showed both the available disk space and the processor queue information for the same systems.
An unrestricted list of performance counters which were available for these systems is shown in the graphic below:
It would have been easy to create a single performance view which would have displayed the available disk space for the systems, and another performance view which would show the processor queue information for the systems. My goal however was to provide a single performance view that showed both. So I started working with this idea. When creating a performance view you can specify that it has a specific object name or a specific counter name. I wanted the counter for “Free Space” and the counter for “Processor “ items. The goal was to provide these counters: (but no others)
- Processor Queue Length
- % Processor Time
- % Free Disk Space
What I found is that you can use brackets to define what acceptable letters are for the item you are configuring. As an example, if you know that you wanted to get something that had the letters a-z in them you can specify this with [abcdefghijklmnopqrstuvwxyz]. In my case I wanted to restrict enough to get these three but no more. So this is how the query was created/I determine what would create a unique condition based upon these counters:
Free Space Processor Result
f p [fp]
r r [rr]
e o [eo]
e c [ec]
e [ e]
s s [ss]
p s [ps]
a o [ao]
c r [cr]
e [e ]
Combined these form: (nope, sorry not Voltron for my fellow geeks out there. But you gotta wonder when Hollywood is going to jump on that particular boat).
[ ][fp][rr][eo][ec][ e][ss][ps][ao][cr][e ]
As shown below:
The result was the view showed only the counters expected as shown below:
Summary: You can use  to specify criteria when defining performance views in OpsMgr. You may not need it often, but this is another tool to keep in the toolbelt if you need it.