Business Service Monitoring views
BSM Grid View navigation
You can access BSM Grid View from the Monitoring menu.
BSM Grid View
The BSM Grid View displays Business Services sorted by ascending status. A BSM with an offline state will be marked with a red color and will be positioned at the start of the grid.
In this view, you can page through the list of BSMs using the paginator at the bottom. You can also change the zoom level which will change the number of BSMs listed on the screen, using the drop-down selector or the plus/minus buttons - when you make a change the view is reset and you will go back to page 1.
A typical BSM will show the user information including status, availability, and operational details of the business service. For the possible statuses of each service, please see BSM Service Status in Priority Order.
Sort and filter
By default, the grid view is sorted by ascending status and is not filtered.
In this view, using the first icon in the top right-hand corner, you are able to sort your BSMs in ascending or descending order.
You can sort by:
- Status (with a sub sort by alphabetical ascending).
- Availability (then status ascending).
- A-Z (then status ascending).
The second icon allows you to filter your BSMs. You will be able to narrow down the BSMs that you are looking for by searching by their name or status; you are able to search by both name and status at the same time.
As you make changes, the URL will update with your chosen options so you can bookmark your view.
You can access the classic BSM view by clicking on the button in the page toolbar:
This will open a new browser tab.
BSM Detail View
The page shows a detailed view of the selected Business Service and its Components including Status, Availability, Impacted and Acknowledgement states. This view also shows the Operational Zone of each Component as a grey box, allowing you to see how and why a particular Component is impacted.
By default, a collapsed view is presented. The components can be expanded individually or by using the toolbar in the top right of the screen to reveal more details.
There are various buttons in the toolbar which can manipulate the BSM tree:
|Collapses all nodes in the tree, except the business service. This button will be highlighted when all nodes are collapsed.|
|Expands all nodes in the tree. This will be highlighted when all nodes are expanded. Note, this button is disabled if there are more than 2000 nodes in the tree.|
|Toggles into All Problem view. Button will be toggled while in this view. Press it again to come out of All Problems view.|
Different icons are used throughout these view which can give immediate insight into the state of any object.
BSM Service status
These are the icons used to indicate the BSM Service status and are listed in priority order
One or more components are offline.
One or more components have at least a failing host.
One or more components are in downtime, and additionally, one or more components are impacted.
One or more components are offline but have been acknowledged.
All impacted components have been marked as acknowledged.
One or more components are in downtime, and additionally, one or more components is impacted but also acknowledged
One or more components are in downtime.
The BSM is online.
BSM Component status
These are the icons used to indicate the BSM Component status and are listed in priority order.
There are more hosts offline than the availability threshold allows.
One or more hosts are offline, but the number of remaining online hosts is above the availability threshold.
The component is offline, but all offline hosts are acknowledged.
The component is impacted, but all offline hosts are acknowledged
At least one host is in downtime and no hosts are offline.
The component is online.
These are the icons used to indicate the Host status and are listed in priority order
There are more hosts offline than the availability threshold allows.
The host is offline, but all critical service checks are acknowledged.
The host is in downtime and is currently offline.
Host is online.
These are the icons used to indicate the Servicecheck status and are listed in priority order
Critical service check.
Critical service check which has been acknowledged.
Service check which is in downtime and is currently critical.
Service check either in OK, Warning,or Unknown.
These are the line types used to indicate relationships between objects.
|Offline, when its child node is hovered over.|
|Impacted, when its child node is hovered over.|
|Offline, but acknowledged, when its child node is hovered over.|
Host status on a collapsed BSM Component
Host status Grid features:
- Shows hosts which are Online, in Downtime or Offline. Colors match Host colors used in other parts of the UI.
- Hosts are sorted in the order: Online, Offline, Downtime going from top left to bottom right, row by row.
- Grid maximum size is 20 by 5, therefore it can display a maximum of 100 hosts.
- The shaded area shows the resiliency threshold of the component. Colors are as follows:
- Red for an offline component.
- Grey for an online component.
Host status on an expanded BSM Component
A border is drawn around all hosts for a component and a bar is shown to indicate the resiliency threshold.
In either the BSM Grid View or the BSM Detail View, you can right-click an object to get a context menu containing available actions to take on this particular node. This works for all BSM tree node types (Service, Component, Host, Service Check).
Choosing a menu item will open a modal window, with the exception of a Recheck for a Service Check where a request will be submitted immediately.
The following table shows all possible actions that can be taken from within the context menu:
|Investigate||Business Service (Grid View)||None||User will be taken the detail view for the service.|
|Recheck||All||ACTIONSOME or ACTIONALL||Recheck modal window will be shown for services, components and hosts. For a service check, a recheck request will be submitted immediately. You may get an error if you do not have permission for the service check.|
|Acknowledge||All||ACTIONSOME or ACTIONALL||Acknowledge modal window will be shown. For a service check, you may get an error if you do not have permission for the service check.|
|Schedule Downtime||All||DOWNTIMESOME||Downtime modal window will be shown. For a service check, you may get an error if you do not have permission for the service check.|
|Go To Host||Host||None||User will be taken to the Navigator view with the particular host selected and the Checker showing all this Host’s Service Checks.|
|Investigate||Service Check||None||User will be taken to the Navigator view and open the Investigate window for the Service Check.|
The modal window consists of an action-specific form (if applicable) and two accordions to help you choose which objects to apply the action to.
The action-specific forms are detailed below.
The Status Selection accordion is used to filter the Service Checks based on their status. You can choose any number of status pills or the All pill.
The Manual Selection accordion can be opened to select or deselect specific Service Checks. The initial list of Service Checks will be based on the status pills chosen in the Status Selection accordion. The table will display the Hostname, Service Check and its status.
The text next to the Submit button states the total number of Service Checks selected. The Submit button will only be enabled if objects have been chosen and the form is valid.
When the recheck has been submitted, a notification will appear in the UI:
If a Service Check is already handled, the Acknowledge menu item will be disabled:
Service Checks that are handled (either due to being in an OK state, already acknowledged, in a scheduled downtime, or the host is in a problem state) will not be listed and cannot have an acknowledgment submitted for them.
Additional data is required when setting an acknowledgment:
- Comment — this is a free form field to add notes related to the acknowledgment.
- Send Ack Notification — if enabled, when the acknowledgment is applied, notifications will be sent to all users that have received problem notifications for the Service Check.
- Sticky — if enabled, the acknowledgment will remain until the Service Check changes into an OK state. If disabled, the acknowledgment will be cleared when the Service Check changes to any other state.
When an acknowledgment has been submitted, a notification will drop down in the UI to show the action has been triggered.
Data is required to set downtime for a service check:
- Duration - How long the service check will be in Downtime. (defaults to 1 hour). Options are:
- 30 mins
- 1 hour
- 2 hours
- 4 hours
- 8 hours
- 12 hours
- 1 day
- 1 week
- Start time — when the service check will go into downtime (defaults to the next hour on the hour).
- End time — when the service check will come out of downtime ( start time + duration).
- Notes — why the service check is going into downtime.
All dates and times are shown in the user timezone.
When downtime has been set, a notification will appear in the UI to show the action has been triggered:
BSM Service and Component Status and Availability
Service and Component status features:
- Format of message:
<STATUS> / <percentage of availability>% AVWhere:
- STATUS is one of the following OFFLINE, ONLINE*, DOWNTIME*, DOWNTIME, ONLINE
- (asterisk against the status) indicates the node is impacted
- AV is shorthand for availability
- If the name of a service, component or host is longer than 30 characters, it is concluded with an ellipsis (
...) after the 30th character
The UI will receive changes to the BSM status at most every 10 seconds by default.
Status changes will be reflected in the current view of the graph, maintaining the current expanded/collapsed nodes and zoom level. However, nodes may move around if they need to be re-sorted.
Configuration changes, where components, hosts or services checks are added or removed from the BSM, will result in the whole BSM tree refreshing. At this time, there will be a notification to indicate that a configuration change has just occurred:
All Problems View
In this view, any components, hosts or service checks that are not in a problem state will be filtered out. This allows you to focus on issues that are affecting the BSM.
Objects that will be shown are:
- Service Checks, Hosts or Components in an OFFLINE state, but not acknowledged, or
- Hosts or Components in an ONLINE state and are IMPACTED
When you first go into the All Problems view, the tree will expand out the failed service checks. To avoid overwhelming the tree for large BSMs, there is a limit of 30 impacted Service Checks.
Host status grids and host resiliency thresholds are hidden in this view.
You can use the Expand All and Collapse All buttons while in this mode.
The nodes will retain the collapsed/expanded state, so when status updates are received the same nodes will be open/closed. However, as the ordering may change, the tree may change the structure.
When you come out of All Problems view, all objects will be collapsed.
NoteDue to the asynchronous nature of the Opsview monitoring engine, it is possible that a service check will be in a critical state, but the BSM component host is not updated to reflect - this means the service check will not appear in the visualisation until the host is shown. Conversely, a component host could be in a failed state but the service check is OK so the service check will not be attached to the host.
- On first load or configuration change, the tree will be centred and only services and components will be visible. If you have a large number of Components, the zoom level will change, to allow you to view as many of them as possible, whilst maintaining the readability of the labels so some components may not be visible
- When the expand all is selected, the zoom level will change, to allow you to view as many of the BSM tree nodes as possible, whilst maintaining the readability of the labels.
- When navigating around the BSM tree, when you click on an element (Component or Host node) it will centre on that element. You are not able to left click to collapse or centre on the Service node and Service Check node.