...

It was concluded that having one perspective is tedious for the future UI. Thus, it was decided to create 2 logical perspectives, which will be separated by the user operations. The first perspective would be "Analyze Perspective"“Analyze Perspective”, where the work of the user would be concentrated on the analysis of the gathered performance data. Second perspective would be "Instrumentation Perspective" “Instrumentation Perspective” where the user can work with Configuration Interface. With this, we clearly separate the type of work a user is performing in each perspective.

...

The only thing that needs to be shared between perspectives is a component that will provide the management of the servers (repositories). Currently, this is done quite "dirty"“dirty”, and it is often not clear what will be the outcome of, for example, repository removal or update.

...

Analysis perspective

The analysis perspective will have more views. All views in this perspective can be minimized, maximized and closed (reopened). The initial perspective layout will have all view on the left side of the screen in tab arrangement, and editors on the right side. The user can freely arrange the position of editors/views later.

Repository Explorer view

Repository Explorer view is the current Server View in inspectIT. Thus, a user can here explore all the agents on the server with a sub-tree of possible actions. This view would only have small changes. First, the shelf organization of the available repositories will be dismissed, by allowing user to selected the wanted repository in the view menu. Thus, only one repository will be visible at time. Furthermore, there will be the update action in the view menu, that would update only the currently visible repositories, and not all of them as the case is now.

...

Storage Manager view

This view is, as name suggest, responsible for managing the storages. The view does not display the data that is stored on the storage, but more provides general options for manipulating storages that are residing on the repositories defined in the Repository Manager.

...

Then we have a set of functionalities to manipulate the storages on the CMR, meaning that a storage can be created, opened and closed on specific CMR.

Last we have option from "mounting" “mounting” a storage to the UI. Mounting means that the necessary data for exploring the storage is downloaded from the specific CMR to local disk.

Storage Editor

Double-click on the storage in the Storage Manager view should open the Storage editor, which displays all information for a Storage and enables user to add/remove the labels for the storage. Storage editor can be in the form of a pop-up.

Storage Manager & Editor combined

There is possibility to combine the storage manager and storage editor in one pop-up window, similar to the Eclipse preferences page. This is a secondary solution, where the storage manager view would be on the left side and storage editor on the right, showing the data about the Storage that is selected in the manager. This can maybe ease up the implementation.

Storage Explorer

The storage explorer has the same functionality as the repository explorer, with difference that it is only showing the data from a already mounted storages. It basically has the same look as repository one, where the only difference is that there is no refreshing possibility, because the data in the closed (and mounted) storage is for now fixed.

Load test comparison

Still to be analyzed

Configuration Interface Perspective

The configuration interface perspective will actually be designed as it was proposed for the Configuration Interface. The only change will be the management of repositories, and it will be as described already. Everything else, will stay the same.