This blog provides an overview of the main improvements delivered with Focused Insights SP3 (ST-OST 200 SP3) for SAP Solution Manager 7.2 SP8.
Please note that customers running Solution Manager 7.2 are strongly encouraged to update to SP7 or SP8 before January 2020 in order to maintain the communication with the SAP Support Backbone.
The default Focused Insights Launchpad is organised per dashboard model; one folder per model (Operation, Tactical…) contains all corresponding instances.
While it is a good entry point for dashboard administrators and technical users, it is usually not the view we want to publish to other teams of the organisation who just consume the dashboards without caring mush about the underlying models of dashboards they are looking at. It makes a lot more sense to organise the launchpad based on the teams structure, the geography, the topic…
With SP3, you can now create your own launchpad and structure it with folders and add and mix instances from any dashboard model supported by Focused Insights.
You can create as many custom launchpads as you want and publish them with a direct read-only URL, as you can do already with dashboard instances.
Operation Dashboard Wizard
Focused Insights Operation Dashboard offers real-time monitoring views of the landscape components.
While this dashboard is highly customisable, it can require significant configuration effort depending on the size of the managed landscape and the amount of metrics and alerts to include.
With the wizard, you can now generate in few clicks an Operation Dashboard that covers a part or your complete landscape.
The dashboard is organised with a predefined structure, where the systems are presented at first level and the alert and metric categories (Availability, Performance, Exceptions, Configuration) are presented at second level. On the floor level, we can choose to add all alerts and metrics activated on the system or only a subset corresponding to an Operation Catalog.
With the wizard, an Operation Dashboard on a large landscape can be setup very quickly.
While the predefined structure won’t fit to all customer requirements, it is a best practice structure that should be relevant in most of the cases. Moreover, this is a great way to setup an experiment the dashboard on large landscape in only few minutes.
The dashboard is generated in the configuration like any other instances; it means we can rework and modify the generated configuration afterward.
Service Level Reporting dashboards are now configured from predefined catalogs. We don’t need anymore to manipulate data providers and complex metric details from SLR Dashboard, instead, we just pick a preconfigured template metric from one of the catalogs available (i.e. “System availability”) and we copy it into the dashboard instance.
Once the metrics have been added to the dashboard, we can customise them with minimum effort by entering the following parameters:
- Metric dimension value (depending on metric type, which system does the metric apply to? which transaction does the metric apply to?..)
- Service level target (e.g. minimum system availability is 99.5%)
- Time frame and resolution (e.g. last month with daily resolution)
- Type of chart for detailed view (line chart or column chart)
Building a catalog of metrics is done from an OCC dashboard. A catalog is nothing else than an OCC dashboard instance flagged as “Discoverable”.
Any metric that can be build out of data providers can be tested conveniently in the OCC Dashboard and re-used later on in the SLR Dashboard.