When you open the Web Console – the default view will open to a “Monitoring Overview” pane. This view, in very large environments, can take considerable time to finish loading, before you can select any other views. Sometimes, loading this view may time out as well.
Here is a way to load a specific view by default. This helps when you have customers that only need to see a very specific pre-configured alert or state view.
The format is:
Lets break that all down:
The first part of the URL is a constant – this should be self explanatory:
The next part is an ID for the view. These will be constant for default built in views and views from Microsoft MP’s. Your custom MP’s will have their own unique view ID’s. I will talk more about how to find these ID’s below. My example ID is for the “Active Alerts” view at the top of the console view list.
The last part is the ViewType. This describes to the console if we are dealing with an AlertView, StateView, or PerformanceView
Here is a SQL query – to get all the view ID’s from the OperationsManager (OpsDB) for any view:
select vv.id as 'View Id',
vv.displayname as 'View DisplayName',
vv.name as 'View Name',
vtv.DisplayName as 'ViewType',
mpv.FriendlyName as 'MP Name'
from ViewsView vv
inner join managementpackview mpv on mpv.id = vv.managementpackid
inner join viewtypeview vtv on vtv.id = vv.monitoringviewtypeid
--where mpv.FriendlyName like '%default%'
--where vv.displayname like '%Service%'
order by mpv.FriendlyName, vv.displayname
Here are some examples of some built in views:
“Active Alerts” view at the top:
“Windows Computers” state view:
“Operating System Performance” view from the BaseOS (Microsoft Windows Server) MP:
Now – you can give a specific use this URL for their favorites – if they want to open the Web Console on this specific view.