This is the second of the four part series that describes how to create custom groups to scope the Operations console, used through the rest of this series:
- Part 1: Creating Custom Groups
- Part 2: Using Custom Groups to create Views
- Part 3: Using Custom Groups with Subscriptions & using one-off notifications
- Part 4: Using Custom Group to secure Views
This blog post creates customized views that use the group created in the first part of this series.
The first step is to create a view folder using the naming convention of <_><Function> (such as _Security since this is for the Security team) under the top level of the monitoring pane. Store the folder in the management pack already created for this function. This approach puts the folders at the top level first in the list alphabetically, making them easier to locate.
Create an alerts sub-view under the new folder that was created (this same wizard is used to create the diagram, performance, state and dashboard views which follow):
Define the view to be limited to the group that was defined earlier, and limited to all alerts that are Not Equals 255 as a resolution state (all non-closed alerts).
Now, create a diagram sub-view under the new folder you created. Define the diagram to the target of the group that was created and to display two layers in a North South configuration.
Create a performance sub-view under the new folder. Define the view to be limited to the group defined earlier.
Create a state sub-view under the new folder, and define the view to be limited to the group defined earlier.
Next, create a three view dashboard with the state, alerts, and performance sub-views under the new folder.
The unpopulated dashboard is shown below. Click each area to add the views to the dashboard. Add the state view at the top, alerts in the middle, and performance in the bottom.
After the dashboard is populated, it should look like this:
The result of this is a customized dashboard, which displays the health, alerts and performance for the servers owned by the Security group. The next part of this series will take the concept of using this group and discuss how to integrate with subscriptions and one-off notifications.