Operations Dashboard 7.2: ST-OST 200 SP06
Operations Dashboard 7.2: ST-OST 200 SP06
Operations Dashboard 7.2: ST-OST 200 SP06
1 Introduction..............................................................................................................................4
2 Configurations ......................................................................................................................... 5
2.1 Configuration Views............................................................................................................................... 6
2.2 Metadata Configuration ........................................................................................................................ 6
2.2.1 Add or Edit Attribute ............................................................................................................. 7
2.2.2 Delete Attribute ..................................................................................................................... 7
2.2.3 Add or Edit Attribute's Value ................................................................................................ 8
2.2.4 Delete Attribute's Value ........................................................................................................ 8
2.3 Catalog Configuration ........................................................................................................................... 9
2.3.1 Add or Edit Catalog ............................................................................................................... 9
2.3.2 Delete Catalog ....................................................................................................................... 9
2.3.3 Add or Edit Catalog's Metrics and Alerts........................................................................... 10
2.3.4 Delete Catalog's Metrics and Alerts................................................................................... 12
2.4 Operations Configuration.................................................................................................................... 13
2.4.1 WebDynpro Configuration .................................................................................................. 13
2.4.2 Configuration of a new instance from the dashboard......................................................29
2.5 Color rating interpretation ................................................................................................................. 30
2.6 Configuration Consistency Check ...................................................................................................... 32
2.6.1 Run Self Check.....................................................................................................................34
2.6.2 Run Self Check..................................................................................................................... 35
3 Dashboard .............................................................................................................................. 37
3.1 Instances View ..................................................................................................................................... 37
3.2 Scenarios View .....................................................................................................................................38
3.3 Dashboard Layout................................................................................................................................39
3.3.1 Header ................................................................................................................................. 40
3.3.2 URL parameters ..................................................................................................................42
3.3.3 Instance Selection Header..................................................................................................42
3.3.4 The Content Area ................................................................................................................43
3.4 Content Navigation ..............................................................................................................................44
Operations Dashboard comes with add-on ST-OST under the group Focused Insights (FI). It's one of the many
dashboard models in FI, which allows one to monitor their systems in real time through predefined key
performance indicator (KPI)s, metrics, and alerts in SAP Solution Manager.
These predefined factors belong to different monitoring points in SAP Solution Manager, including:
· Metrics and Alerts from:
o Business Intelligence, SBOP Monitoring
o Business Process Monitoring
o Connection Monitoring
o Early Watch Alerts Integration
o Interface Channel Monitoring
o Job Monitoring
o Process Integration Monitoring
o Solution Manager Self-Monitoring
o Technical System Monitoring
· Key Figures from Business Process Monitoring.
· KPIs from Business Process Analytics' (BPA) Panel, EEM, and OCC Queries (defined based on OCC
Dashboard).
· Tickets' rating in ITSM.
The dashboard model comes with 2 views. The Instances View and the Scenarios View like below images.
You can configure different instance of the dashboard model to fit your views of monitoring. Each instance is
composed of at least 3 levels.
The first 2 levels are for organizing your point of monitoring, for example, level 1 can be for systems, level 2 can be
for functioning areas.
The 3rd level is for the actual predefined KPIs, metrics, and alerts. In this level, you can configure to have the 4th
level, which only appear in the dashboard, by grouping.
We will get to this in details in section for Operations Configuration View.
· Metadata Configuration
· Catalog Configuration
· Operations Configuration
· Configuration Consistency Check
These tabs will be described in the details in the up-coming sections.
In this view, you can create metadata for level 1 item, which can be used for Scenarios View of the dashboard.
The metadata is composed of attributes. An attribute is represented as a scenario in the Scenario View of
Operations Dashboard.
Each attribute can have multiple values. These values are referred by level 1 items in Operations Configuration.
These values are shown as tiles in Scenario View. Each tile will have level 1 items that refer to this value.
Attributes Table
· To add a new attribute, select button. You can add as many rows as you want.
· From this point, you can edit the existing attributes, or newly added attributes. When you are done editing,
always select button to effectively apply your changes.
· You can then select button to be back to Read-only Mode.
You can delete an attribute by select it in the Attributes table and choose button. A popup will appear to
prompt your deletion of the attribute.
You can only delete an attribute, if it exists (with attribute id assigned and not 0). The newly added without saving
when you're in edit mode cannot be deleted as it's not existing.
· To add a new value, select button. You can add as many rows as you want.
· From this point, you can edit the existing values, or newly added values. When you are done editing, always
select button to effectively apply your changes.
· You can then select button to be back to Read-only Mode.
You can delete an attribute's value by select it in the Attributes' Values table and choose button. A popup
will appear to prompt your deletion of the attribute. You can select multiple rows to delete.
In this view, you can create catalog for metrics and alerts configuration, which can be helped to speed up the
process of configuring of application operations in Operations Configuration View.
· From this point, you can edit the existing catalogs, or newly added catalogs. When you are done editing,
always select button to effectively apply your changes.
You can also add/edit/delete metrics, and alerts in Catalog Configuration table for the selected catalog (even
for newly added catalog). You need to select the catalog first to do it. Please refer to section 2.1.2.3 for this
task.
· You can then select button to be back to Read-only Mode.
You can delete a catalog by select it in the Catalog table and choose button. A popup will appear to prompt
your deletion of the catalog.
· To add new metrics, and alerts, select button. This will bring up Metrics/Alerts search help
dialog as in image below.
o First you need to provide the entry point. Choose button at the end of the Entry Point input field to
bring up Entry Point search help like in image below.
o Choose the desired Monitoring Use Case in the drop-down box. Select button to list the
available entry points. You can also check the list of possible entry points in Alert Directory Browser
of Solution Manager.
o Select a managed object in the table and choose to select the entry point.
o Now choose a managed object where we can get the metrics and alerts from. Choose button at the
end of the Managed Object input field to bring up search help like in image below.
o Select a managed object in the table and choose to select the managed object.
o If the selected managed object is of type Technical System, you can check the checkbox
to have additional metrics and alerts from instances and hosts related to the technical system.
o The list of metrics, and alerts available in the managed object should appear in Metrics / Alerts table like
in image below.
Note
Please be note that the showing metrics, and alerts do not show the specific managed object which they
were selected from. This is because we are configuring a catalog, so we care only about the managed
object type, so that later we can apply these metrics, and alerts to the entry point when we do Operations
Configuration regardless the actual managed object.
You can delete catalog metrics, and alerts by select them in the Catalog Configuration table and choose
button. A popup will appear to prompt your deletion of the metrics and alerts.
This view is where you configure the real instances of the Operations Dashboard model. As mentioned before,
each instance is composed of 3 levels.
The first 2 levels are for organizing your point of monitoring, for example, level 1 can be for systems, level 2 can be
for functioning areas.
The 3rd level is for the actual predefined KPIs, metrics, and alerts. In this level, you can configure to have the 4th
level, which only appear in the dashboard, by grouping.
In the level 1 panel, now with title System as provided previously, do as follow:
Note
You can assign multiple values from one or multiple attributes to this level 1 item.
In the level 2 panel, now with title Category as provided previously, do as follow:
· Application Operations (System / Metrics tab): based on the Technical Monitoring templates that are applied
for that system. The dashboard will read the latest status rating from the metric/event store.
· Business Process Monitoring Key Figures (Key Figures tab): The rating relies on the current status of the key
figure.
· Business Process Analytics KPIs (BPA KPIs tab). This requires that a BPA dashboard panel be configured.
The data is read using the existing BPO dashboard connectors.
· EEM tab: which is configured by selecting robots from a list according to the EEM type. This includes selecting
a scenario and script consisting of one or more steps, or a particular scenario and script and step.
· ITSM tab: which is configured by providing searching criteria on the tickets.
· OCC Queries tab: Provide integration with OCC dashboard by using the query which can be used in OCC
Gadget to select the last data available for rating.
The following sections will describe how to add these KPIs to the dashboard.
To add Application Operations (AO) metrics or alerts, the technical monitoring needs to be done for the system.
This means the relevant templates need to be activated. The steps are as follows to add an AO metric or alert:
· Make sure the needed level 2 item is selected.
o Look for entry point by select the search button next to Entry Point input.
o A dialog will be shown, where you can look for entry point based on monitoring use case as shown in
image below.
o Select button to list the available entry points. You can also check the list of possible entry
points in Alert Directory Browser of Solution Manager.
o Select a managed object in the table and choose to select the entry point.
o Provide description to the entry point.
o Provide catalog to tell the entry point to inherit metrics and alerts from catalog. The configuration of
catalog is provided in section 2.1.2.
o If the chosen managed object is of type Technical System, the check box "Auto propagate to instances,
hosts and database" will appear. If this is checked, all instances, hosts, database, database instance and
database tenant instance ‘metrics, and alerts in the catalog belong to instances, hosts, database,
database instance and database tenant instance of this technical system will be inherited also.
o Now you can either:
o Add new entry point by select the button. A new item will appear in the table on the
left-hand side.
o Apply changes to the selected entry point by select the button.
· In metric/alert section, select the button to go into edit mode.
Note
If you use catalog in the entry point, it's not necessary to do this step as metrics, and alerts will be
inherited from catalog at run time. To show inherited metrics/alerts, use the button
in Entry Point table toolbar. You still can do this step if you want to add additional ones which are not in
the catalog.
Metric/Alert Configuration
o Choose a managed object where we can get the metrics and alerts from. Choose button at the end of
the Managed Object input field to bring up search help like in image below.
o Select a managed object in the table and choose to select the managed object.
o After managed object has been chosen, select the search button next to Metric Name input box to
look for Metrics and Alerts to add. A dialog will be shown as in image below, where you can select multiple
Metrics and Alerts.
· Add your level 2 item or go to a previously added level 2 item and add the same system again as shown
previously.
· Then right click on the system in the table and select the option Paste system’s metrics:
Then the system metrics will be copied, and you should them in the table below. The reason that you need to go to
a previously configured system is that it is possible to have steps or interfaces with different metrics configured.
Once the copy is done it is still possible to add or remove another system metrics.
To add a Business Process Alert to the level 2 item, select the Key Figure tab. The steps are as follows to add Key
Figure:
· Make sure the needed level 2 item is selected.
o Select the source in the Solution Documentation as an entry point to look for key figures. Select the
search button next Solution Documentation text. A dialog should appear as below for you to select the
entry point.
o Key figures should be listed now in the key figure search help. You can choose multiple key figures and
edit their properties. Use the arrow buttons to add to and remove from key figures selection on
the right-hand side.
· Due to the restriction of UI, not all selected key figures are shown. To review, or edit your selection, click the
Key Figure search button again.
· Select button to effectively add selected key figures. And the newly added key figures will
appear in the list of key figures on the left-hand side table.
The prerequisite to configure a Business Process Analytics KPI is that a Business Process Analytics KPI Panel
needs to be configured. This can be done in The Business Process Operations work center and then select the link
Setup Dashboards.
Once a Business Process Analytics KPI has been configured, then it can be added to level 2 item for monitoring.
Select the BPA KPIs tab, the steps are as follows:
· On the right-hand side, the fields are enabled to edit for KPI selection.
o Choose a panel by select the search button next to Panel input. A dialog box will appear as shown in
image below. Choose a panel.
The prerequisite to configure an EEM is that a robot is selected from the list of robots. This can be done in the
Robot section and then for a scenario select a script consisting of steps in the KPIs section.
Once an EEM has been configured, then it can be added to Step or Interface for monitoring.
The steps are as follows:
· Select the EEM tab and select the button to go into edit mode.
· On the right-hand side, input description.
· Select a Type of EEM.
o If Availability is selected, you can choose Script in the list of KPIs.
o If Performance is selected, you can choose Step in the list of KPIs.
· Choose the jump to option to specify the navigation in the dashboard when this EEM KPI is selected.
· Select button to effectively add selected EEM KPI. And the newly added KPI will appear in the
list of KPIs on the left-hand side.
In ITSM, we want to monitor how many tickets based of the filters provided has passed the threshold provided or
not and reported the dashboard.
To add an ITSM, follow the steps below:
o We can compare IRT or MPT with the threshold to rate the ticket. Choose either IRT or MPT.
o Provide thresholds to rate the ticket in G2Y (yellow rating), and Y2R (red rating) inputs.
o Choose Grouped option if you want to group all tickets found together in one tile in dashboard. Otherwise,
all found tickets will appear in dashboard.
· Select button to effectively add selected KPI. And the newly added KPI will appear in the list of
KPIs on the left-hand side.
There is a very good dashboard model in Focused Insights group called OCC Dashboard. It provides a dynamic
way of selecting monitoring data through query. We want to leverage it in Operations Dashboard also. The idea is
to have a query which is usually configured for a gadget and rate the last data point from this query based on
configuration in Operations. And then we can always jump to this gadget for details view of the query.
To add an OCC query, follow the steps below:
· Provide the query in Query input field. Normally you can get it in OCC Gadget Configuration.
· Input Name
· Input Description.
· Provide the thresholds for rating.
· Provide Time range, just like in OCC Gadget Configuration.
· Provide Resolution, just like in OCC Gadget Configuration.
· Selection Jump to option.
· Select button to effectively add the query. And the newly added query will appear in the list of
queries on the left-hand side.
Dashboard Header
Then do as follow,
Configuration dialog
System’s Configuration
Once the operation of the creation is done successfully, choose to be redirected to the new instance.
Level2 tiles
In the level 1 and level 2, the color rating can be easily interpreted:
Ø Red = Critical or High level of severity
Ø Yellow = Medium level of severity
Ø Green = Low level of severity
But as soon as we navigate in the metrics and alerts level you can encounter additional rating indicators, which
concerns only alerts. These rating indicators depend on the configured severity of the alert and its status:
postponed or transferred.
The red and black striped rated alerts are those whose severity is lower than the severity configured by the user
they are considered as ignored alert.
The yellow and black striped alerts are those whose severity is lower than the severity configured by the user
they are considered as ignored warnings.
The green and white striped alerts are those that were postponed, no matter if initially they were red or yellow,
after the postponement they all will look the same (green and white striped). Thus, they are considered as green
Ps : the previous rating of the alerts is not reflected in the upper levels, it means that if you have a red and white
striped alert and a pure green or red alert or yellow, the upper levels will reflect the green/yellow/red one and
won’t consider the striped ones.
In this view, you can check the consistency of the operation dashboard configuration, which can be helped a lot to
speed up the process of finding the causes of some issue detected in the operations application.
• Propose fixes:
o Auto-fixes: Either the entry can be replaced easily and automatically, or it will be deleted in the
configuration.
o Manual: This issue needs to be manually fixed. Typically, the jump-in to non-existing gadget.
o Auto-fix log: The fix will be logged. However, we do not store the log, hence it will be lost if you refresh the
configuration application.
For each instance you can use the expand option to see the root cause of the issues found. And for each problem,
there will be check box for auto -fix to be selected if you want to use the auto fix option.
Note: Be careful with auto-fixes which have Fix Type of "Manual/Auto". This type, in general, will delete the entry if
you choose to auto-fix it. So be sure you want to do it.
You should carefully check each issue and decide whether to use the auto-fix option or not as there may be auto-
fix to delete the entry in your configuration.
You can use the select all auto fixes/deselect all auto
fixes buttons in order to select/deselect all check boxes at once.
You can use expand all / collapse all option to open or to close the issues
reports.
When we click on the button run auto-fix a pop up of confirmation appear containing two
buttons the button OK and cancel.
Once the configuration has been done, you can access the dashboard to see what you have configured. There are
2 views of the dashboard you can use. To access the dashboard based on the view, please follow section 3.1 and
3.2.
The first view is the Instance View. The dashboard will show level 1 items by instances. You can access it by using
Focused Insights Launchpad as follow:
· Select Operations tile.
· Select the instance you want to go to, and select button Go to Dashboard.
Once inside the dashboard with selected instances, you will see as below:
You can switch between instance by clicking the title of the instance. The first level of the instance is, as in
configuration, composed of level 1 items. Each level 1 item is 1 tile. The content of the tile can be as simple as an
icon to show the rating of the level item, or it can be the aggregated number of alerts and tickets. This is based on
the configuration of the instance as shown previously.
As shown before, the dashboard model has another view called Scenarios View, where scenarios are attributes,
and content of first level view is attribute's values. You can access it by using Focused Insights Launchpad as
follow:
· Select Operations Scenario tile.
· Select the instance you want to go to, and select button Go to Dashboard.
Once inside the dashboard with selected instances, you will see as below:
When you enter the application, the selected instance in the below screenshot will be the page by default:
Operations Dashboard
Dashboard Header
· User Settings button with user name as label. When chosen, it pops up a menu:
User's Menu
Here is the parameters list that can be added to the application URL to perform the activities described below:
· ColorScheme=Dark to select dark mode (ColorScheme=Light is the default mode)
· fullScreen=X to display dashboard in fullscreen
· refreshTimer=X where X is the refresh time to set in minutes (By default, the refresh time is the selected one
in the configuration application)
· autoSwitchOnIdle=true/X working with carousel feature, it enables the auto-switching between the
displayed instances (autoSwitchOnIdle=false by default)
· hardRefresh = X ' (X = number of hours) This option is used in order to clear the browser cache after a
configurable period.
Ø In IE, the Browser will be closed and restarted again in order to reinitialize the memory.
Ø In chrome and other browsers, the browser will be refreshed after the X hours.
· statuses=<status1>, <status2>… Enable to display only the tile(s) with the selected status(es)
Example :
[Protocol]://[domain:port]/sap/bc/ui5_ui5/stdf/ope_dash/index.html?configId=1& statuses=red
Ø It shows the tile(s) with red status.
· font=extend to display the tile’s text in two lines.
Note
Starting from SP05, the user has the possibility to navigate directly to the wanted level by clicking on it from
the webdynpro configuration application or by adding its ID to the URL.So navigation URL will have this format
ConfigId-XXXXXX-XXXXX
Each instance will have its own refresh timer which is a circle icon containing the time set in minutes.
You can click on the refresh icon to manually manage the timer refresh instance.
The content area is in the middle-center of the dashboard. This is where you see the content of the selected
instance.
Content Area
· The Filters button , It enable filtering tiles based on Status, Metric Categories (appear at metric level),
and Metric Types (appear at metric level).
Filtering option
· The expand all tiles button . It will un-collapse the tiles.
· The refresh button . It serves like the refresh button in instance selection header.
As you know, there are two views in the dashboard model. The Instances View and the Scenarios View. In the
Instances View, at first level the tile are level 1 items. You can click the tile to navigate to the second level which
shows the level 2 items for selected level 1.
However, in the Scenarios View, each tile is the value of the scenario. Inside each tile, the level 1 items will be listed
as entries of the tile. To navigate to the second level, you need to select an entry in the tile.
From second level, the navigation is the same for both views. When you reach the third level, some of the tiles
allows you to navigate to the fourth level, some does not. It's based on the type of metric, and the grouping
configuration. In general, if you encounter a KPI tile like image below, you can navigate to the fourth level.
Otherwise, it will jump to the place where it's configured in the configuration application. You can differentiate
them by the arrow on the right side, and the additional 2 numbers information in the tile. These numbers are for
the total of red, and yellow rating that this tile contains. They appear only when rating is yellow or red.
While navigating down, the navigator will keep track of where you are, and where you were by navigating items.
You can go back 1 level by select the left arrow button. You can also click to any navigating item to go back to that
level. In case the screen size is small, so not all the navigating items are shown. You can select the "…" button to
open the list of now shown levels.