The scope section within the configuration of many tiles allows you to define what is shown by that tile. For many tiles the scope is mandatory, but for some such as API tiles, it is optional as it can be used to filter the results further.
For information about scoping tiles on perspectives see How to scope tiles on perspectives
There are three ways of defining the scope:
- List - one or more objects (or groups to show top level health status)
- Group - show the members of a group
- Advanced - specify a group or class or both, along with criteria such as InMaintenanceMode = 'TRUE'
It is worth noting the following points:
- Users will only see in SquaredUp what they are allowed to see in the SCOM, which is controlled by role-based access control (RBAC).
- The Performance Scalar tile should be scoped to only one object using the list option, not to a group, tag or type, as only one figure is shown.
- Wildcards can be used to help search for objects in the scope list.
List allows you to search and select one or more individual objects to show.
Start typing and after two characters all object names which contain those characters will be listed for you to select from. You can add one or more objects to the list to be shown. To remove an item click the x to the right of the item.
For example, for the Status tile you may wish to list two individual servers:
If you select use the list option to select a group then it will show the status of the group itself, rather than the objects within the group:
Search and select a group. Only one group can be selected. For the Status tile the group members, i.e the objects within that group, are shown. To see the status of the group itself use the list option to search and select a group.
By default the scope of Performance tiles will look at multiple levels of membership (recursive search) for objects, so they will look at multiple-levels of membership rather than just one level, i.e. it will show objects that aren't directly contained in a group, but are contained within other objects. This means the tile shows data for objects that aren't directly contained in a group, but are contained within other objects. For example, this allows you to find disk metrics when scoped to a server.
If the scoped group contains only subgroups and you have not specified a class, then no metrics will be available in the metrics drop down list. By specifying a group AND a class it means that you can extend this recursive search to use top-level groups to show graph data for objects within sub-groups (as well as objects).
To enable recursive searching to work for sub-groups you should specify a group AND a class in the Advanced Scope. This will allow the dropdown list to show the metrics for the objects in the sub-groups.
The advanced scope has the additional options of specifying class and/or criteria.
You may choose to display objects by class, rather than the objects in a particular group. Either the Class or Group (or both) must be defined. The class text box equates to target class within SCOM.
As you type the dropdown will be populated with a filtered list of classes from SCOM, from which you can select the required class.
For example, for a Status tile you can use the class 'Group' to see the health state of all groups.
Choose your class carefully as for a Performance tile this will determine which metrics are available in the Metric section.
This allows you to create an expression to further refine the scope.
There are so many ways you can filter the scope using the criteria, such as:
- Objects that are not healthy: HealthState != 1
- Objects in maintenance mode: InMaintenanceMode = 'TRUE'
- Objects with a name starting with the same characters: DisplayName like 'test%'
- Or to exclude a particular server from the specified group: DisplayName not like '%server3%'
For more information see:
Perspectives - a page level scope
A perspective is an object-level dashboard where the information is shown in the context of a specific object. When you browse to an object in SquaredUp you will see several perspectives which show different views of the same object (or group), each showing a focused set of information.
Because each perspective has an object context (e.g. the application, group or server) tiles are automatically scoped to that object and there is no need to separately scope each tile.
Can I use Wildcards when searching for objects in the scope?
By default searching will look for the top 10 items containing the words listed in the search. If you wish to create a more specific search you will need to use wildcards (*).
If you provide a wildcard after the term you are looking for, it will find all the objects which start with that word searched and any terms that may follow, an example of this can be seen below.
The same applies if the wildcard is placed at the start of the search, it will look for objects that contain the searched word and which also have terms before that word, see the following for clarification.
If you enclose your searched term in wildcards it will look for objects which contain the searched word, this object will not begin or end with the term searched.
No values found for the given metric for the last <time period> at the resolution '<raw/hourly/daily>'
You may get the
No values found for the given metric message returned if you change the scope after setting the metric.