_{Detailed system information with list of servers}

At the bottom of this tab, there is a list of servers. This list provides an overview of servers, their names, if it is an application server or a database server, whether there is a host name given, the number of the CPU(s), RAM size, as well as locality and description. In the column 'Don't mon.', if there is a flag, then the server is excluded from monitoring.

Collector jobs tab

The Collector jobs tab displays all created Collector jobs for monitored systems and provides information regarding their statuses. From this tab, Collector job runs can be controlled and monitored.
In the list of Collector jobs, following information is displayed:

SID – determine system ID for which Collector job has been created.
Profile – which customizing is in use for the Collector job, i.e. what KPIs is being checked?
Job status – informs about status of background job of Collector job. Background job can have these statuses:

Not running – No scheduled job.
Scheduled – Job schedule run created for Collector job.
Waiting – Collector job informs that a job is waiting for free work processes for running.
Running - Collector job is currently running.

Period value / Period type – informs how often a Collector job is running.
Button – If a Collector job is scheduled, the user can click stop button is required which stops and cancels the scheduled job.
Button – If Collector job is not running, the user can click the start button to run the Collector job.
Execution – Determine if Collector job is executed immediately or scheduled on specific date and time.
Start date/Start time – date and time of initial run of the Collector job.
Retention time – specifies how old collected data will be stored by Collector job. Data older then retention time are automatically deleted with the exception data, which are collected in saved time intervals.
Background Job Name/button – name for background job of Collector job. Clicking on this button will execute transaction SE37 with displaying of this job.
Job last status/Last status icon – specifies about status of last background job run. Can have these statuses:

Finished - specifies that the last background job of Collector job was successfully finished.
Aborted - specifies that the last background job of Collector job was terminated by error or cancelled by user
Not running - specifies that the background job of Collector job was not started before.

Delay[s] – specifies of any background job delay in seconds while waiting for a free work process.
Run date/Run time – specifies the date and time in which background job of Collector job is started
Duration – specifies how long the background job of Collector job was running.

Collector jobs tab

Last delay – specifies about last background job delay in seconds when it was waiting for free work process.
Last run date/Last run time – specifies the date and time when last background job had been started.
Last duration - specifies how long the background job of Collector job was running.
Remaining time – specifies the time in seconds in which the next run of Collector job will occur.
Next run date/Next run time – specifies the date and time of next Collector job run.
Create date/Create time – specifies the date and time of creation of background job for Collector job
Creator name – specifies who started/stopped background job for Collector job.

If the user double clicks on Collector job record in the list, then all information is displayed in detail in the bottom section of Collector job tab.
In the top bar, the menu of Collector job list is available which contains all standard buttons for working with ALV list and which allows the user to sort, filter etc. In addition, a refresh button is available along with information about last time of refresh. This button gets actual status of all background jobs.
To modify or delete a Collector job, the user can right-click on the Collector job record and from the menu that displays, it is possible to delete or modify the selected Collector job by choosing the required option.

_{Context menu on selected Collector job}

Before deletion of Collector job the following pop-up is displayed.

Pupup to delete collector job w/o data _{Pop-up to delete Collector job w/o data}

If you click Yes,del.data, then all data collected by this Collector job is deleted. When you click No,keep data, then only Collector job is deleted but data can be still loaded into charts.

Modify Collector job will display Collector job manager for current Collector job where definition of Collector job can by changed. The process of starting the monitoring is described in a separate section called "Start monitoring".

Only Collector job that is not running can be deleted! Deletion of Collector job will remove all collected data with exception of data collected in saved time intervals.

KPI charts tab

All collected KPIs of monitored systems are represented in the form of charts within this tab. In these charts, you can directly see the behavior of monitored KPI with respect to the time.
When the tab is chosen for the first time, then all data about KPI, which is necessary for displaying of charts, are loaded. Progress of loading takes some time and it is displayed in the status bar in the bottom left corner of the screen. KPI data are loaded only once for each KPI chart. This indicates that KPI chart is displayed faster during the second time, because the system uses the cached data.

Each chart describes one measured KPI in a selected 'time interval' for systems and/or servers that have been checked in the 'system tree'. The chart has the KPI's description at the top, X-axis represents a timeline and the Y-axis represents measured values. The unit of value is displayed after the KPI description at the top in brackets (next to the chart title). A legend is displayed by clicking on a grey square on left side in each chart. The legend describes the colored series, which represents the checked system(s)/server(s).

KPI charts

By right-clicking on the KPI chart area, the KPI context menu is displayed. The user can use all available functions which were described in the KPI Context Menu chapter.

The measured KPI can be defined for a system or for a server as follows:

If only one system/server is checked, then one line will be displayed to represent the KPI.

_{System's KPI in a chart}

If KPIs of multiple systems/servers are displayed in one chart, then each individual system or server will be represented by a separate colored line. In the legend, you can see which colored series is associated with which system or server.

Server's KPIs in a chart

The number of charts per page can be selected by choosing a predefined layout. Possible grid layouts are 1x1, 1x2, 2x2, 3x3 and 4x4. The grid between charts is also resizable by dragging the mouse.

_{Grid layout choosing}

Depending on the number of KPIs, these charts are not only placed on one page but on several pages. The user can switch between pages using the and buttons found on the top left corner of the chart displayed in the KPI tab.
The KPIs, which are displayed in the grid layout, is determined by selected KPI group or specific KPI in KPI tree. Each group consists of KPIs and other subgroups. The correct page is set automatically.

Displaying KPI charts in grid layout by selecting KPI in KPI tree

The amount of data loaded and displayed in charts on the page has some limits. The limits aren't determined by application server resources but resources (mostly memory) on the fronted PC. In general, it shouldn't be a problem to display 16 KPIs (grid 4x4) with data from 1 system and all its servers for a 1 month time period. In the case the amount of data reaches its limits, the charts aren't refreshed and the following pop-up appears.

Pop-up when charts are frozen

After clicking Less data, the system refreshes the screen and displays only one KPI chart (grid 1x1) for the selected systems and time period. After clicking Same data, the system tries to refresh the screen with the existing selection. If the refresh with the same data leads again to screen freeze, then the pop-up will be displayed again.

KPI mix tab

By using the KPI mix tab, the user can see the behavior of more KPIs together, by graphically comparing dependencies between all measured KPIs, for example, the dependence between the CPU load and work processes.
When the KPI tab is selected, the user may then check to display an active KPI in KPI tree (note that a system/server must also be selected in the system tree). Once a KPI is checked, it will be displayed as a chart of mixed KPIs and assigned to a new colored series.
When KPI or system/server is unchecked, the appropriate series will be removed from the chart. Allowing the user to create and customize a comparison chart based on individual needs. All KPI series are portioned in the same manner similar to the KPI tab charts specified by KPI definition.

_{Checked KPI in KPI mixer}

You can find associations of colored series to KPIs in the legend at the bottom of the chart. These colors of series are different from the previous KPI tab.

Messages tab

The message tab displays the status messages created by Datavard Insights, for example, during the collection and processing of KPIs from a monitored system. Each message is described by a text containing information about when it occurred, on which system or server and the type of message (in ID column). Three standard types of messages exist:

- OK / successful messages
- Information / alert messages
- Error messages

The messages displayed are dependent on the systems/servers that are checked in the system tree.
Towards the top of the Messages tab, there is a list box in which the user can filter the message group. By default, all messages are displayed and in addition there are the standard ALV operations such as sorting, filtering, aggregating etc.

_{Monitor Messages}

Details tab

This tab contains additional information collected from the monitored systems. All this information of the same kind is categorized and placed into one table. By clicking on a specific table, all the information is displayed in an ALV list from the table. With this ALV list of messages, it is possible to do all standard ALV operations like sorting, filtering, aggregating and so on.

If the selected table is server dependent only data of the particular server is displayed. Please see more in the section System and KPI Tree part Detail tables.

Detailed information from monitoring

Alerts tab

The Alerts tab displays messages during monitoring and collecting of KPIs, where an event occurs to one or more specific KPIs' values. Messages of events wherein the KPI's critical values that reach or exceed the threshold limits, which is set by the user. Listed below are some examples of such events:

Massive short dumps within a short period of time
System downtime or unavailability
System stops/restarts
A typical peaks or downs in system performance
Start/end of SLO operations (conversions or migrations)
Users working in the system during conversions and many others

Such events will be in a state of occurrence as long as corresponding KPI values are outside of the threshold limit. If events hold for a long time, the alerts will keep informing the user that such events are still occurring and allows the user to keep track and monitor the event's progress.

Through an event occurrence, the process is recorded and stored within the alerts tab. There, you can find an ALV list of occurred events. Each line of the list represents one event. It has information about the system and the server (if the KPI of the event is server-specific). There is also an icon that informs about alert statuses as follows:

- Success event
- Warning event
- Issues event
- Error event

In the next column, there is a count of occurred event alerts. There is always the number one if an event occurs for the first time. The next columns indicate when an event has started and when it has ended (if it has ended). The last column is an event's description.

_{Occurred events}

With this ALV list of messages, it is possible to do all standard ALV operations like sorting, filtering, aggregating and so on.
For more detailed view on event, just double click on the line in ALV and detailed output will be displayed.

_{Detail output}

Browser not supported