(DI-1802) Start default monitoring

Add a new system

To add your systems to the Monitor, follow these steps:

1. In the main application toolbar, click on or press (Shift + F1). A pop-up for adding a new system appears.

2. Select the main system type.

_{Select system type}

3. In the Destination field, type the name of the RFC Destination. It is mandatory to fill this field with an existing and valid RFC Connection type "ABAP Connection" to proceed with the following steps.

 You can use the Maintain RFC button to open the SAP standard transaction which maintains the RFC connection.

4. After specifying the RFC Destination field, click on the Check RFC button. The system checks the connection to the remote system. If the connection is present, the system displays additional information about the remote system in the fields below. If there are connection problems, or if the remote system does not have the Insights collectors package installed, the system displays an error message.

5. In the Maximum time for RFC PING in the seconds field you can set up a maximum time for RFC PING. When the remote system does not respond after the maximum time set here, then a red light icon in the monitoring pool highlights that the system is not accessible.

_{Adding a new system}

6. A Monitoring area is a functional unit used for monitoring. It determines which information is collected from a particular monitored system. See the examples in the above figure.

(Optional) You can change or add Monitoring areas by clicking on options in the Monitoring areas field.

7. You can change or add server types by choosing options in the External server types for monitoring field.

8. Check whether all information is correct. Finally, click on the green button Add system or press F8 function key. The new system will be added to the monitoring system pool.

_{New system in the monitoring system pool}

Once the system is added, you can start the default monitoring by clicking on Start default monitoring. This action executes all collector jobs with pre-setup KPIs and default times which are defined in default profiles.

In some cases the following dialog appears. It informs you that the displayed KPIs are excluded, because of the reason mentioned here. You can proceed by clicking on Exclude KPI.

When you a select a particular system on the right side you can view all the information about this system. In the lower part of the Monitor you can view information about system servers. You can find here the subtotal values of the fields Count of CPU and Physical memory.

Delete a system from the monitoring pool

This step removes a monitored system from the monitoring pool as well as all its Collector jobs as well as deletes all collected data including saved intervals. Before deletion you must stop all running Collector jobs linked to the monitored system.You can stop the Collectors jobs in the tab Collectors Jobs through the Stop button .

_{Removing a monitored system from the monitoring pool}

_{Warning in the case Collector jobs are not stopped before deletion}

_{User confirmation before final removal}

Additional Monitoring Settings

Create a Collector job (for monitoring)

To schedule the monitoring of a remote system it is necessary to run a Collector job for monitoring. This Collector job is scheduled and periodically run as a background job. To create a Collector job follow these steps:

Under the Collectors Jobs tab click on the  button or press the function key F9.
The system displays a pop-up dialog known as a Collector job manager. This has two sections namely Monitoring plan (for creating/ editing Collector jobs) and Running Collector jobs (providing an overview of already created/running Collector jobs).

_{Collector job manager}

To create a new Collector job, you should define the following:

• Definition: Enter a System ID which should be monitored and assign a Monitoring profile.
• Execution: Choose to run the Collector job immediately after the Collector job is (re)started or choose a time and date indicating when to begin.
• Period: Define the time interval between the Collector job runs.
• Retention time: Determines how long data will be stored on the Central monitoring system. In the moment the retention time has elapsed, data will be deleted. The only exception is data with a time stamp that belongs to a time interval which you specified before.

When the Collector job has been created/ edited, click the (Re)Start Collector job button. A notification appears in the bottom left-hand corner.

_{Successfully started monitoring Collector job}

System settings maintenance

When you click on the  button in the RFC or press Shift + F5, the system displays the System maintenance screen. On this screen it is possible to maintain relevant system settings.

In the left side under System maintenance you can change the RFC Destination, the response time (Timeouts) and the Description.

_{System maintenance}

Correct setup of response time is important in the case there is a slow connection between systems. If the response time is exceeded, then the system is displayed as offline or inaccessible. You can access this window with a double click on the Timeouts field by the particular system.

Setup of response time

Server list displays list of servers for a selected system. Here, it is possible to specify which server(s) should be monitored.

_{Server list}

Assigning a Monitoring area to a satellite system

When a satellite system is successfully added to the list of monitored systems, assignment of the Monitoring area is done automatically. Only in some cases (e.g. upgrade to a new Insights version with new Monitoring areas) you should assign the Monitoring area manually by following these steps:

1. Go to Settings > System Settings (Shift + F5).
2. Select the system that you would like to assign a Monitoring area. Double click on Monitoring areas in the dialog structure tree.
3. Click on New Entries (F5) button. 
4. Add the new Monitoring area.

5. Press Enter and save changes.

With the assignment of a new Monitoring area to a monitoring system it is possible to collect area specific KPIs.

Assigning a system to a system group:

This step allows you to group systems, based on common attributes such as, production, development systems, geographic location etc. Note that one system can be placed in multiple groups.
When you assign a system to one group or remove it, it will be reflected in other groups to which the system is assigned as well.

1. To  choose or add a new system group click on the New Entries button. When you create a new system group you must fill in all the required fields. Select the system group to which you would like to assign systems and afterwards double click on the System group list.

 _{System groups}

2. In the System group list enter new system(s) which belong to the selected group by clicking on the New Entries button. 

 _{System group list}

_{Example of graphical distribution of groups in system tree}

Configuration of parameters:

By selecting Configuration in the tree, it is possible to customize the behavior of some predefined properties:

Max. runtime for execution of collecting BG jobs in seconds
Determines the maximum runtime for the execution of collecting background (BG) jobs. If BG job runtime reaches this time limit, it is aborted. The default value is 600 seconds (10 minutes). 
Allow use KILL WP for long-running collecting BG jobs
Allows to use the OS level function "KILL Work-Process" to terminate collecting BG job which cannot be aborted with the standard functionality. Works only if the previous configuration parameter "Max. runtime for BG job agent..." is not specified. Set this parameter to 'X' to turn it on. The value is by default empty.
Priority class for execution of collecting BG jobs 
Sets BG job priority class for execution of collecting BG jobs. There are three priority classes used: 'C'-lowest priority, 'B'-medium priority, 'A'-highest priority. Default value is 'C'. If the value isn't specified, the priority is the same as by default value 'C'.
Server group for executing collecting BG jobs
Specifies the name of a server group on which BG jobs are executed. A server group must be created by the SAP transaction SM61. It determines a specific list of application servers on which BG jobs can run. The value is by default empty (no specific server group is used). 
Warning: If the server group is not set correctly (doesn't exist in SM61) then the execution of collecting jobs fails.
User ID used for execution of collecting BG jobs
Sets the user ID which is used for execution of collecting jobs. Each execution of collecting jobs and all actions of monitoring on the central system are performed under this user ID. If a user ID isn't defined (default value), then the ID of logon user who triggers the execution of collecting BG job is used. In the case that the user ID is not valid, the system displays the following error message "Can not start background job! Reason: <user ID> does not exist."
It is recommended to create a system type user on the central monitoring system and set it up with limited authorizations which can be defined in the role /DVD/MON_ADMIN.
When the set user ID used for the execution of BG jobs is deleted, all affected jobs start failing. Insights is able to detect these failures and display them by marking the particular line with a red icon in the 'Collector jobs' tab in Insights Monitor. Also the affected systems are marked with a red icon in the list of monitored systems. Please note: For the correct run of collector jobs, it is important that the user ID is not deleted or locked.
Name of the cleanup job
Specifies the name of the BG job which cleans up all transactional data according to retention dates. Retention date for all collected data is calculated based on retention time (in days) which you set in collecting BG jobs' definition. This cleanup job is scheduled and executed only once per day (starting time of this job depends on the next setting "Starting time of cleanup job"). Purpose of this cleanup job is to delete all transactional data which has it's retention date older than the date of the cleanup job execution.The goal of this cleanup job is to have on the system only data which fulfills the retention period. 
Starting time of clean up
Specifies the starting time of the BG job to cleanup all transactional data according to retention dates. When you change the starting time to a time that already passed that day, the cleanup job is rescheduled to the next day. The time must be set in the following way: <HH:MM:SS>. 
External storage ID in Datavard Storage Management
This setup allows to store monitoring results in a different (external) transparent storage with the help of Datavard Storage Management (DVD SM). You must define a Storage ID in DVD SM through the transaction /DVD/SM_SETUP. Monitoring results stored on external storage are protected against retention deletion. Only transparent storages are supported. For more information about DVD SM please contact our consultants.The value is by default empty (no external storage is used).
Maximum allowed percentage of used aRFC resources
Insights checks the system and server availability using asynchronous processes [aRFC] to prevent communication freezes. Each system has a limited number of dialog worker processes (75% is the system default value, check the transaction SARFC for details) which are used for aRFCs. This setting determines the maximum number of aRFC resources that can be used by Insights availability checks. If Insights requests aRFC resources, which have exceeded the configured limits, it waits until aRFC resources are available again. The waiting time is set in the following configuration parameter. If the waiting time is exceeded, the availability check is not performed and an error message is written to the log. This setting should be applied only in the case when the Insights central instance runs on a system with limited resources or on a system which uses aRFC by other transactions. The value is by default empty. 
Max. waiting time to check available aRFC resources 
Defines waiting time in seconds, to check if aRFC resources are available for the Insights availability check. This parameter works only in combination with the previous configuration parameter. The value is by default empty. (no waiting time, availability check and collecting job are canceled when aRFC resources aren't available, error message is written to log).
E-mail address used for sender of notification
E-mail address which is used as a sender in notification emails. Default value is do_not_reply.com@datavard.com (same e-mail address is used, if the value is not specified). 
Warning: If you enter an invalid e-mail address, no notification emails will be sent.
Display popup for user in different time zone.
Informs the user that there are time zone differences between the system and the user (default 'X' value). If the parameter isn't set, a pop-up won't appear. If parameter is set to 'Y', the pop-up is displayed and the Insights Monitor is closed.

In Dependent configuration each value of the properties mentioned above can be set for a specific System ID or a Profile or a combination of both. In the case there are present several rows with the same System ID or Profile, the Property value is loaded according to the following rules:

1. Property values with a specified System ID and Profile (both fields are not empty) have the highest priority.
2. Property values with only specified System ID (Profile field is empty) have a medium priority.
3. Property values with specified Profile (System ID field is empty) have the lowest priority.  

_{Configuration property setup for specific SID / Profile}

Example:

The configuration property AGENT_MAX_RUNTIME has the default value 600 seconds (After this time limit the BG job will be aborted).
The first row sets the value for each collector job with the profile DEF_1MIN for each system except the NSD system (higher priority has the second row as it has the same profile and additionally the specified System ID "NSD").
The second row overrides the value for the system NSD and the profile DEF_1MIN, it also overrides the property value of first row for the profile DEF_1MIN.
The third row overrides the value for each collector job executed for the system NSD and any profile of the system except the profile DEF_1MIN, which is defined in the second row. The third row overrides as well the fourth row, as a property value with a specified System ID has higher priority then a property value with a specified Profile only.
The fourth row overrides the default value for each collector job with the profile DEF_5MIN and on every system except the NSD system, as the third row has a specified System ID and therefore has a higher priority.

Licensed functionality

If you want to use our advanced functionality in monitoring (Finding correlated KPIs or alerting based on anomaly detection), you should type a valid license key into the field “License key”. To receive this key, please contact our customer support.

After you complete all the above steps, you can use our advanced functionalities. If you don't complete them, you will get an error message that this type of  function is not licensed. 

Restriction in monitoring:

This step enables you to turn off the monitoring / alerting during a specific time interval, for example to perform the system maintenance. You can set the restriction for a particular system, server, profile or alert.

_{Restriction in Monitoring Overview}

To create a new entry click on the New Entries button and specify the following:

• The Restriction Name: Describes the reason for switching off monitoring
• Restriction rule is valid from: Time validity of the rule (date range in which this rule is valid)
• Time of occurrence: You should specify the exact time in which this rule should be executed. You have the option to choose a repetition of this rule per days, weeks and months
• Purpose of restriction: Two options are available: to Pause monitoring or to Pause only alerting
• Apply restriction only on (combination allowed): You can specify the System ID, Server name, Monitoring profile and Alert name (only in the case of alerting pause). You can use a combination of all of these fields. In the case you don't specify the fields, the monitoring / alerting of all systems will be skipped during the specified restriction time.

 _{Restriction in Monitoring - Input Screen}

Time intervals:

You may save time intervals in order to maintain a historical reference of issues that may have happened in the system landscape. If there were any time intervals saved, then they would be displayed in this section. 

_{Time intervals}

 _{Time intervals in monitoring main screen}

Message groups:

In Message groups, the user can adjust or create categories of messages and with these groups; the message list is adjusted or created. The user can view the messages generated by monitoring activities in the message tab.

 _{Messages groups}

 _{Messages list}

Message notification:

The user can create notifications to be sent to users/distribution lists whenever a notification occurs.

 _{Message notification}

User List

Here you can define what the user can view in the Insights cockpit. It is possible to define for each user a filter for specific system, system groups, profiles that are accessible and the KPIs that they can see. Each user may have setup own system status KPI which will be used for indication of system status in Insights Fiori application.

 _{User List settings}

 =>
 _{Setting up User Filter for System ID's} 

=>
_{Setting up User Filter for KPI groups}

=>

`

_{Customized view in Insights cockpit}

Monitoring settings maintenance

When you click on  Monitoring settings button in the menu bar or press Shift + F2, the system displays the monitoring settings maintenance screen. 

_{Monitoring settings}

KPI Definitions:

A KPI is registered by creating the definition, setting parameters for this KPI and assigning it to a collector, which will collect the KPI. 

_{KPI Definitions}

KPI Definitions include the following parameters:

_{Maintenance KPI definition}

• Definition
  • KPI name: unique name of a KPI
  • KPI description: description that will be used in charts and other outputs as the KPI label
  • KPI collector
  • Collectors description
• Properties
  • Unit: % MB, KB dependent on KPI.
  • Num. of decimals: how the value is displayed in the charts – KPIs are stored as integer numbers and not as real numbers
  • Monitoring area: determines system type specific to KPI. The KPI will be collected only for a specific system type like ERP, BW, CRM, SRM and others
• Collection
  • KPI collector: determines which collector will collect the KPI
  • Collected on: states where the KPI will be collected or calculated. Possible values are Remote system and Central system
  • Collected for: determines KPI orientation. Values are either system or server
  • Server specification: information can be collected on any server, only application server, only database server, only external server
• Calculate KPI from another KPI(s)
  • See Automatic calculation below.
• Chart settings
  • Lower/Upper limit mode:
    • Limit is calculated from minimum/maximum values
    • Limit is fixed value
    • Limit is calculated from fixed and minimum/maximum values
  • Lower/Upper limit value: value for displaying KPI series in charts
  • Chart line type: simple line, spline, discrete
  • Logarithmic Y scale: Y axis labels are values of common logarithm (decimal)
  • Don't display KPI in charts: KPI won't be displayed

_{Long description}

 Automatic calculation

In this block, it is possible to define the method in which the KPI will be calculated without any coding. With customizing, the user can define a new KPI (e.g. new percentage value), which will be calculated from already calculated KPIs defined in source fields. The calculation is setup in "Calculation function" field and source KPIs are defined in three fields below:

• "KPI source for calculation"
• "2^nd KPI source for calculation "
• "3^rd KPI source for calculation".

_{Automatic calculation}

Usage of these fields depends on the chosen calculation function. It is possible to use following calculation functions by default:

• Minimum from all servers – new system KPI will be calculated as minimum from KPI's values of all servers defined by KPI name in first source field and are collected in current run.
• Maximum from all servers – new system KPI will be calculated as maximum from KPI's values of all servers defined by KPI name in first source field and are collected in current run.
• Averages from all servers - new system KPI will be calculated as average from KPI's values of all servers defined by KPI name in first source field and are collected in current run.

_{Example for average calculation for 
KPI DISK_RESPONS_SYS - Average disk response time (all servers)}

• Sum from all servers - new system KPI will be calculated as sum of KPI's values of all servers defined by KPI name in first source field and are collected in current run.
• Minimum from collected KPIs - new system/server KPI will be calculated as minimum from KPI's values of all system/server defined by KPI name in first source field and are collected in current and previous runs.
• Maximum from collected KPIs - new system/server KPI will be calculated as maximum from KPI's values of all system/server defined by KPI name in first source field and are collected in current and previous runs.
• Average from collected KPIs - new system/server KPI will be calculated as average from KPI's values of all system/server defined by KPI name in first source field and are collected in current and previous runs.
• Percentage from all servers - new server KPI will be calculated as percentage from KPI's values of all servers defined by KPI name in first source field and are collected in current run. Percentage is calculated from KPI's value in server as base of sum of KPI's values of all servers.
• Percentage of one KPI from other KPI - new system/server KPI will be calculated as percentage from KPI's value of server/system defined by KPI name in first source field in current run and in base of KPI's value of server/system defined by KPI name in second source field and which are collected in current run.

Example for percentage calculation for 
KPI ENQ_ENTR_P - Usage of SAP lock table

• Delta between last and current KPI value - new system/server KPI will be calculated as delta between KPI's value of server/system, defined by KPI name in first source field and collected in current run and previous run.
• Absolute delta between last and current KPI value - new system/server KPI will be calculated as absolute value of delta between KPI's value of server/system defined by KPI name in first source field and collected in current run and previous run. Result KPI's value is always positive.
• Speed of increasing of KPI value from last run in minutes - new system/server KPI will be calculated as delta between server/system KPI's value of server/system defined by KPI name in first source field and collected in current run and previous run. Result value will be divided by time between both runs.
• Calculate difference between two KPIs - new system/server KPI will be calculated as difference between KPI's value of server/system and defined by KPI name in first source field and server/system KPI's value defined by KPI name in second source field.

The user can use the third field to facilitate the calculation of more complex KPI. Allows the users to avoid coding and to create simple calculations of KPI by only customizing/defining – how to interpret/compare values and for these to be displayed in graphical format.

Assign alerts & Alerts:

You can create new alert definition or assign alert. To create new one go to 'Alerts' and if you want to assign we recommend to go under KPI definitions into Assign alerts. Subtree for both options has same functionalities and is based on same principle.

_{Alert view}

_{Alert detail}

This definition consists of:

• Alert name and description
• KPI name and description – this description will be used as the label in outputs.
• Alert type – describes the type of alert and determines the icon to be displayed if the alert occurs. Possible values are:
  • Success – 
  • Warning – 
  • Issues – 
  • Error - 
• Period time – the frequency that specifies how often the alert is rechecked.
• Changelog

For every alert created, it is necessary to define associations to the KPI and to the Profile. This can be done in the Treshold setup or Anomaly view category of this screen, according to the type of alert. 

The following fields should be filled:

• Monitoring profile – alert will be checked only for this profile under running Collector job.
• KPI name – alert will be checked only for the value of this KPI.

Comparison operator – determines in which case a KPI value causes an alert to occur.

_{Comparison operator}

• Threshold – determines the limit value for a KPI. This alert will occur if the KPI exceeds its defined threshold of associated alert.
• Unit – determines the unit of measurement to be used, i.e. %, MB etc.
• Duration start – how long can a KPI value exceed the threshold (in grey area) before an alert will occur (starting delay for alert).
• Duration end – how long a KPI value has to be outside of the threshold area (in grey area) before an alert will be stopped (ending delay for alert).

_{Treshold setup}

Each alert occurrence can be notified by email or by message in SAP Business Workplace. That can be done in the Alert notification category of this screen. The following fields should be filled:

• Monitoring profile.
• Recipient address – the email address or username from SAP system can be specified.
• Type of notification – determines the notification method. Possible values are:
  • E-mail – notification will be sent to the email specified in "Recipient address" field.
  • SAP Office message – notification will be sent to the SAP Business Workplace for user who is specified in "Recipient address" field.
  • Private distribution list – notification will be sent to all addresses defined in SAP Private Distribution List (transaction SO15 or button "Distribution list" in Insights toolbar).
  • Shared distribution list– notification will be sent to all addresses defined in SAP Private Distribution List (transaction SO15 or button "Distribution list" in Insights toolbar).
• BAdI ID – [optional] ID, which will be used for filtering of BAdI call. You can create your own BAdI for notification using BAdI implementation /DVD/MON_BADI_DEF_EVENT. Each BAdI implementation has to define the filter, which is also used for determining explicit call of the BAdI for processing of notification. Default BAdI implementation used for notification has initial BAdI ID.
• Alert notification – determines the period for sending of notifications. Possible values are:
  • At first occurrence – notify when alert occurs first time
  • At next occurrence – notify each occurrence of alert
  • At end of alert – notify when alert is completed

^{Alert notification}

Inputs & rules

Here you can define Input table name and rules.

^{Input tables}

^{Change rules for KPI and profile}

Parameters

^{Define parameters}

Assigned groups, profiles, detaiils

Assign KPI groups, profiles and detail tables to KPIs.

Profiles definition:

The user may create new profiles or maintain existing profiles. These profiles are required before starting the monitoring of Collector jobs.

_{Profile definition}

By selecting a profile, the user may customize KPIs, Alerts, Collector's parameters and Collector's setups associated with the profile. Using these profiles, you can define the KPIs which will be collected in the monitored system. Only existing KPIs can be associated with specific profiles.

_{Association of KPIs to profile}

If you want to monitor a certain KPI for a specific profile, you can also set alerts. Only created and KPI-specific alerts can be set up in this method.

_{Alerts created for profile-dependent KPI}

In this subcategory, you can define a profile to determine which alert will be monitored with specific setup for a specific KPI. For detailed information about alerts, refer the next section Alert definition.

KPI groups

KPI Groups category with KPI Group list subcategory defines only the categorizing and displaying of KPI's charts on KPI tab. It is possible to customize the views so you can adjust which KPI groups are visible for you in the Insights cockpit; this can be done in the "Filter for KPI" group as well as in the "Filter for Profile". To create KPI group press 'New Entries', fill required fields and save. To display and then edit 'List of KPIs' and 'KPI group filter' you have to select one of the KPI groups.

 
^{Montoring settings tree}

Your KPI group settings and assignments are visible on screen tree in Insights cockpit. The tree is build dynamically.

^{KPI groups in Insights cockpit}

Collector settings maintenance

Collector:

To access Collector settings press:

The user can view the central list of collectors. These are the collectors used by Insights to monitor the central and remote systems. List of collectors that are remote or on the system that can be called. Delivered collectors start with the /DVD/MON prefix and are preconfigured. These could be adjusted by the user, by adjusting KPI's, parameters etc. Users can create their own collectors under the Z* Y* namespace and it is mandatory to register each collector here before being used.

_{Collector maintenance}

Collector's KPI:

To access this feature, select the collector and double click KPI folder. It is the list of the KPIs associated to the selected collector, here can be adjusted or new ones created. The user may adjust or set up the additional parameters for these KPIs to suit requirements.

_{Collector's KPI}

Collector's inputs & rules:

These are customizing tables, which contains reference information for the collector, in relation to the type of KPI's that are needed to be collected. The user can customize these tables to watch out for specific requirements.

_{Collector's inputs & rules}

The user can change these inputs by pressing the edit button.

 _{Collector inputs edit}

Detail tables:

Here are displayed detail tables for selected collector. In detail table are stored data collected by collector's KPIs.

^{Detail table view}

Field view contains field details of selected detail table.

^{Field view details}

Here in assignment view you may assign KPI to collector and its detail table.

^{KPI assignment}

Collector's parameters:

Some collectors are created to measure durations taken when a system or server are performing certain operations, this is where the user could use the parameters to set / adjust benchmarks for the KPI's. In this case, values are deleted and the default values provided with the collectors will be used.

_{Collector's parameters}

Collector's setup:

Here, the user can change or define new behaviours of the collectors:
The user can determine the Destination of the collector whether it will be run on the central or remote instance, to suit system differences, as not all behaviours may be required, or the user can collate information and post processing, i.e. post processing of remote systems in the central system.

_{Collector's setup}

Other behaviours could be required in certain instances where Collectors are monitoring systems on a regular basis, for example, every 5 minutes. In such instances, execute it in a separate dialog and set a time limit in order to avoid an overlap of data collected. 
This setup is not necessary in standard cases.

User settings

Users could set up their own GUI of Insights by clicking on the "User settings" button in the main menu.

The system displays a pop up window with two tabs:

• "General" tab contain basic settings.
• "Charts" tab contain settings related to customizing of charts.

General settings

General settings:

Ping system on refresh – The user may check this option and by doing so, on each refresh of the Monitor, the connection to each monitored system in the system pool will be tested. Checking of this option may slow down the response of GUI because all connections will be tested; however, the system displays real time information about statuses of the monitored systems.
Ping application server on refresh – similar to 'ping system on refresh' but it is carried out on application server level; wherein on each refresh of the Monitor, the system will test the connection to each application server in system pool. Checking of this option may slow down the response of GUI because all connections will be tested; however, the system displays real time information about statuses of the monitored application servers.
Set last time interval on startup – if you check this option, then on each run of Monitor, the time interval from last run will be set.
Do not use user's local time zone – If this field is checked, then the user will view all time fields in the monitor in the system time zone of the central monitoring instance.
Hide unused KPI from KPI groups/ KPI Groups – If these are checked, then all unused KPIs/KPI groups will be hidden from the KPI Group tree view on the bottom left of the monitor.
Hide non-monitored servers from pool tree – If this is checked, then all servers which are marked as "Don't monitor" will be hidden in the system pool tree view on the top left of the monitor.

Search Tool bar for System Pool tree and KPI pool tree

A new search bar has been introduced for System pool tree and KPI groups. This is switched off by default; however, you can turn this on via the user settings. The Search bar enables you to navigate to a node of the tree by entering the description/name, for example, in the KPI "CPU" and this will display all KPIs that have CPU within the name.

_{Quick search for SIDs, SERVERs, KPIs}

 Chart settings:

_{Chart settings}

Use java script jqCharts – by checking this option, you will enable new powerful charts, which are implemented via Java Scripts. Using new charts allow more interaction and faster display of huge amount of data in charts. In addition, the charts are clearer and the User can view detailed descriptions of KPIs.

_{JavaScript Charts}

Stretch series – if you check this option, then all displayed charts will be stretched to measured time intervals. This option is possible to use only with new Java Scripts charts. 

Display legend in charts – if you check this option, then in all charts there will be displayed legend. This option is possible to use only with new Java Scripts charts. 
After changing of settings, the user should click on  "Save setting (F8)" save button and all changes will be immediately reflected. If the user closes the Insights cockpit, then all settings with composition of layout, checked systems and selected KPIs will be automatically saved for that particular user and it will be restored in next run of Insights. 
If saved settings are no longer suitable, then click on  "Reset to default settings (F2)" button.