ITelSib IPHost Network Monitor

ITelSib IPHost Network Monitor - Professional Network & Server Monitoring Tool

IPHost monitors your network resources 24 hours a day and alerts you to issues.
With IPHost Network Monitor you can monitor both Windows and Unix based networks, various servers and network equipment, availability and performance characteristics of web and other applications. The advanced alerting system provides timely notifications using several means such as e-mail, SMS, and instant messengers; the system is also able to execute correcting actions locally or remotely via SSH. Reporting and graphs are available through a web interface.
IPHost Network Monitor supports more than 20 monitoring methods and more than 10 alerting technologies. Custom monitors and alerts let you to extend your monitoring systems based on changing needs of your company.
Application templates allow you to create an entire set of monitors on a host in just a few clicks. An application template is a set of monitors preconfigured to check a certain application or service (e.g. MS Exchange) or a server (a Web or Mail server). The IPHost Network Monitor installation contains over 50 standard (predefined) application templates and provides you with the tools to create your own templates.
IPHost Network Monitor includes an add-on product for end-to-end monitoring of web applications and e-commerce web sites – Web Transaction Monitor. This tool simulates the steps of activity of a real user of web application or e-commerce site customer. With Web Transaction Monitor you can check web application availability and performance.
SMS over GSM modem/phone alert allows sending SMS (text message) over GSM modem or phone attached to the computer. This alert is the most reliable mechanism for sending notifications about system failures or serious degradation in application performance.
IPHost Network Monitor software is available in several editions: Basic, Professional and Enterprise. Basic edition has different set of features and limited to 200 monitors. Professional edition is available with 500 or 1000 monitors. Professional 1000 edition includes 5 Remote Network Agents. Enterprise edition comes with unlimited number of monitors and agents.
Below you can find detailed description of main features of IPHost Network Monitor.

Description of other features:
Monitoring Features
Here you can find the list of monitor types supported in IPHost Network Monitor and brief description of their parameters.
IPHost Network Monitor provides constant monitoring of network’s services and resources that are critically important for your company. Unlike many monitoring tools IPHost Network Monitor checks not only the availability of a resource but also its operability and performance characteristics.
The base element in IPHost Network Monitor is a monitor; it checks the availability of a service on a remote or local computer and requests a value of a certain parameter. The monitor has parameters that determine:
1.    monitor name,
2.    monitor definition (what and how should be checked — monitoring parameters),
3.    time interval between polls,
4.    dependency settings: should the monitor change its state after another monitor has changed its state,
5.    what kind of reports should be sent and how often.
You can set the conditions that define when the monitor should change its state on State conditions tab. You can specify what alerts should the monitoring service send if the monitor changes its state or event occurs.

Groups of Monitors
Grouping monitors in accordance with host types and monitor types provides a convenient way to manage the monitoring system. For example, you can create a host group for each location and organize your hosts (servers) accordingly.
Available Monitor Types
SNMP
Standard way of retrieving management information and performance characteristics from Unix/Linux servers, Windows servers, networking and other equipment. 70 common MIBs are provided with the product.
PING
Sends a standard PING to the server/device.
TCP
Checks whether the server accepts connection at the specified port number.
UDP
UDP datagram send/receive on a specific port.
SMTP    
Checks an SMTP server with optional authentication and sends a test message.
POP3    
Checks a POP3 server with optional authentication. IMAP    
Checks an IMAP server with optional authentication.
HTTP/HTTPS
GET or POST HTTP/HTTPS request with optional content validation.
Web Transaction Monitor
This tool simulates the steps of activity of a real user of web application or e-commerce site customer. With Web Transaction Monitor you can check web application availability and performance.
FTP    
Checks an FTP server with optional authentication. DNS    
DNS server monitoring WMI CPU load
Checks current CPU load on remote computer via WMI
WMI Available Memory    
Checks current volume of available memory on remote computer via WMI
WMI Bytes Received/sec    
Checks current inbound throughput on remote computer
WMI Bytes Send/sec    
Checks current outbound throughput on remote computer
WMI Custom (run WMI script)    
Runs custom WMI script to check some value on remote computer
DISKSPACE    
Monitors the free disk space of a local disk drive or a remote network share
FILE    
Monitors a file on a local disk drive or a network share. It checks if the file exists and the file size is in a given range Windows Service    
Monitoring the presence of any Windows service on the local machine or a computer in the network. You can restart the service using the Run program action.
ODBC Database    
Checks an ODBC data source for availability with optional authentication and SQL expression execution. You can use it to monitor Oracle, MS SQL server and other databases. Oracle Database    
Checks an Oracle database for availability with optional authentication and SQL expression execution.
MySQL Database    
Checks a MySQL database for availability with optional authentication and SQL expression execution. Using of secure connection is also supported that is especially important if you monitor hosted database.
MS SQL Database    
Checks a MS SQL database for availability with optional authentication and SQL expression execution.
WMI Traffic Speed    
Calculates incoming, outgoing or total traffic speed (average for a polling interval) on the specified network interface using data provided by the target host WMI service.
WMI Traffic Volume    
Calculates incoming, outgoing or total traffic volume on the specified network interface for specified timeframe using data provided by the target host WMI service.
SNMP Traffic Speed    
Calculates incoming, outgoing or total traffic speed (average for a polling interval) on the specified network interface using data provided by the target host SNMP service.
SNMP Traffic Volume    
Calculates incoming, outgoing or total traffic volume on the specified network interface for specified timeframe using data provided by the target host SNMP service.
Script or Program
Makes it easy to create your own custom monitors. Scripts and programs are supported. You can use Nagios plugins.
SSH (Remote Script or Program)
Allows you to run commands on other computers over SSH and to integrate IPHost with other systems deployed remotely.
SNMP Generic Trap
Listens for the SNMP v1 / v2c traps sent by SNMP-enabled devices such as routers.
SNMP Custom
Monitors the SNMP v1 / v2c / v3 performance counters such as network traffic or system resources on any SNMP-enabled device.
SNMP CPU
Measures CPU usage parameters (total, user time, system time and other parameters) using data provided by SNMP agent on target host.
SNMP Memory
Measures memory usage parameters (free, used for either physical memory or swap space) using data provided by SNMP agent on target host.
SNMP Disk space
Measures free or used disk space for a specified filesystem using data provided by SNMP agent on target host.
SNMP Process
Shows various parameters (number of processes, CPU and memory usage) of specified process using data provided by SNMP agent on target host.
SSH CPU
Measures CPU usage parameters using data provided by SSH script running on target host.
SSH Memory
Measures memory usage parameters using data provided by SSH script running on target host.
SSH Disk space
Measures free or used disk space for a specified filesystem using data provided by SSH script running on target host.
SSH Process
Shows various parameters of specified process using data provided by SSH script running on target host.
WMI CPU
Measures CPU usage parameters using data provided by WMI service on target host.
WMI Memory
Measures memory usage parameters using data provided by WMI service on target host.
WMI Disk space
Measures free or used disk space for a specified filesystem using data provided by WMI service on target host. Note: Unlike generic Disk space monitor this monitor does not require the monitored filesystem to be a network shared resource.
WMI Process
Shows various parameters (number of processes, CPU and memory usage) of specified process using data provided by WMI service on target host.
WMI Uptime    
Shows target host uptime in days according to data provided by WMI service.

Polling
Monitors are polled (checked) with a regularity specified by the user. By default, ‘Basic connectivity’ monitors are checked every 30 seconds, all the rest — every minute. A minimum interval between polls is limited to 1 second, but it is not recommended to use polling interval fewer than 15 seconds because more frequent checks are practically useless, besides, they can lead to the performance degradation of the network or network resources, which contradicts with the goal of monitoring. The result of a check is either a value or an error message. Depending on returned value monitor stays in OK state or turn into one of two problem states:
1.    Performance Warning
2.    Down
IPHost Network Monitor reacts to monitor transitions to problem states by performing alerts assigned by the user to the corresponding state. The alerts are set in Alerting Rules.

Dependencies

You can make the monitor dependent on the state of another monitor. This means that the dependent monitor is checked only if the monitor on which it depends is in a state different from Down, Stopped or Stopped by Dependency. For example, you can make all the monitors in a subned dependent from PING monitor to a gateway to this subnet. By default, a monitor inherits its dependency setting from its parent host, the default dependency is PING monitor on its parent host.

Admin Tools
IPHost Network Monitor provides interfaces to some tools that help you to manage your hosts (servers) from the client GUI directly. There are:
1.    SSH client
2.    Telnet client
3.    Remote Desktop client
You can configure the interfaces on Settings-> Admin Tools page. Also, you can also specify a path to device web interface on a host Main parameters tab.

Application Templates
Here you can find the list of application templates supported in IPHost Network Monitor and their short description.
Templates categories
Application template is a collection of predefined monitors to be created at once. Instances of such templates are called applications; each application has its own node in a main tree. Application monitors perform in-depth checks for a particular type of host or application. For example, there are templates for a generic Windows Server, Microsoft Exchange Server, Apache and IIS web servers, Oracle database server and so on. Application templates are intended to help you creating and maintaining your monitoring system.
An application template can be used in a discovery process. The Discovery Wizard allows to select application templates to be searched for. Each application template contains a set of conditions that define how to process the application during discovery. If these conditions are satisfied the application template is applied to the host.
There are several template categories predefined; apart from existing templates, you can easily define new ones. Please take a look at a section with application templates of our Application Templates Community where you can upload your own application template or download application templates of other users.
Template categories list
Server Health Checks
Domain Controllers
Mail Servers
Web Servers
Database Servers
Virtual Machines
Other Applications And Services
Template categories description
The below templates categories are predefined:
Server Health Checks templates contain common monitor types that can be used to get a general server health result. Failure of any of the recommended monitors, after their performance values are adjusted to required conditions, should be treated as immediate call for action, necessity to solve the reported problem as fast as possible.
Domain Controllers templates allow to check Windows domain implementation, its basic functionality and capabilities. Domains are used not only to provide authentication, but also to support data exchange and other services; problem state of any of them might bring the whole local network to a halt.
Mail Servers templates check availability and security features of mail servers – common set using SMTP/POP3/IMAP4 protocols, as well as MS Exchange.
Web Servers templates allow to watch the general health and state variables of different Web servers (such as checking connections number, resources utilization, etc). Try to utilize as specific template as possible (i.e., use generic template only if working with Web server not listed in this category).
Database Servers templates cover verifying various database engines (MySQL, MS SQL etc), checking their state parameters as well as general connectivity and health.
Virtual Machines templates check host and guest state/consistency; note that checking guests doesn’t mean accessing virtual machine in regular manner, as physical computer: for this particular case a virtual machine is treated as an application running on the hypervisor host.
Other Applications And Services templates include all the services not otherwise mentioned in the above categories, such as SharePoint or Memcached.
Monitoring use cases
templates include typical monitors set; every built-in template name defines the cases where the template is best applicable – try the best match first, otherwise use generic template
if no existing template fits your needs, you can define a new template, and include specific monitors set into it; give template a name clearly identifying its purpose
Monitoring tips
if your mail services used to deliver email IPHost alerts are using domain authentication, then you might be in trouble if domain authentication fails; for that purpose, it is recommended to install local mail server on computer running IPHost monitor, as secondary; for the same reason do not use intranet email as primary notification service, use external email instead
make sure you have two independent outgoing mail servers (MTAs), so that a message could have higher delivery chances, if one of the servers is either down, or inaccessible; using the mentioned locally installed MTA can provide you with fallback mail server, storing a copy of every monitoring message
although there are monitors testing secure data transfer over SSL v2/v3, use the mentioned only for legacy devices, using out-of-date services; try to use only the most safe ciphers, see Cipher List or similar reference services.
when checking resources usage for services like Web servers, Database servers, try to avoid polling too frequently, especially on production servers; for example, if using a query to check database consistency, use as simple query as possible and avoid running it too often
make cheaper to use/access resources: state of service to be monitored can be checked by regularly updating simple to access resource, such as text file: reading that file might be much less resource-intensive than performing actual service checks; for example, command-line MySQL utility can run simple checks and output results into a text file readable on local file system: checking that file can be significantly faster
if running IPHost on virtual machine, make sure to have a second IPHost installation installed elsewhere, checking health of that VM: otherwise, if VM or its host fails, monitoring notices stop to arrive

Network Discovery
Helps you to create a basis of your monitoring configuration and automates the task of detection network hosts and network services.
Automatic network scanner: finds resources in your network
Network discovery tool of IPHost Network Monitor allows to detect and re-detect network devices on subnet, or selective list of IP addresses or hostnames. It only takes 2 minutes to install IPHost and commence discovering hosts to monitor on your network.
IPHost Network Monitor creates base set of resource monitors on your local area network for yourmonitoring system using automatic network discovery. The process finds hosts (using network mask it detects, or IP addresses/hostnames list, if entered) and checks every host for user-defined set of known resources (protocols supported – such as PING, HTTP, SSH, SMTP etc). It also can create WMI or SNMP traffic monitors, if corresponding protocols are detected. Using default set of selected resources allows you to start monitoring your network in a few minutes after having installed IPHost. If regular rediscoveries are set up, you can keep hosts and resources list up-to-date with minimal efforts.

Network discovery wizard
To begin, run discovery wizard: click Discover Network button on toolbar (you’ll have choice of Quick or Advanced discovery), or select Discover Network item from Tools menu (in the latter case, Advanced discovery will be run). The Quick discovery uses default values for all scan parameters, whereas the Advanced discovery allows you to modify scan parameters to suit your network environment.

The above step is only available when there are several remote network gents available (including local agent: main installation of IPHost). Choose which agent to use for discovery.

 

 The next step allows to specify what hosts to scan. IPHost detects network mask of default network adapter automatically; it is also possible to specify IP ranges, subnets in CIDR notation or hosts/IPs list.

On the next page resources can be specified to look for. IPHost will scan network for resources on standard ports, you can also specify additional ports to scan, if applicable.
“Scan for other monitors only if host responds to PING” allows to reduce time required to scan: only if host answers to ICMP PING, will further checks be performed. Note: uncheck that if there are hosts not responding to PING for some reason.
“Activate discovered monitors” allows to run monitors immediately, or left them stopped, so you could review them first and adjust settings as you wish.

The next page allows to specify what credentials (if necessary) should be used. Credentials can be inherited from host or host group, or you can override that by specifying the set of credentials to use.

The final page allows to set up scheduled repeated network scans (re-discovery). It’s self-explanatory; if re-discoveries are required, they can be scheduled on per day basis (all scans will be started at the same time of day).
After all parameters are set, just click on “Scan” to commence the discovery process. The monitoring process continues while network discovery is in progress. The IPHost Network Monitor will create monitors for all discovered resources and start them if the corresponding feature is selected immediately after the discovery process is finished.

Alerting Features
Here you can find the list of alert types (ways of reaction to the problems happened during monitoring) available in IPHost Network Monitor, and their brief description.
Get Timely Notifications: Make Sure Your Servers Are Alive
IPHost Network Monitor provides various methods of automatic response to monitored resource state changes. Prompt and informative notification on a monitored resource operation failure allows you to substantially reduce the downtime of important resources, which saves the users work time and improves administrator work effectiveness.
There are alerts that send a message with information on the problem using various protocols (e-mail, instant messengers, SMS and others). Also, there are alerts that can start a specified program (local or remote via SSH) or set an SNMP value. Using these alerts you can implement any method to react to a monitor state change: from starting/stopping of a service on a remote machine to rebooting it.
Alerts and Simple Actions
All alerts are listed in one common list of alerts. Any alert can be used with any monitor. Each alert is a set of simple actions (e.g. send e-mail, show pop-up) and time schedules assigned to them, so that each action is executed in the specified time interval only. Currently IPHost Network Monitor provides the following types of simple actions to construct an alert:

1.    Send email. Sending an e-mail to persons concerned. Some variables can be used in the message template, such as $MonitorName, $CurrentState, etc., which allows for instance to use one template for all state changes.
2.    Send SMS via GSM modem or mobile phone attached to a computer running IPHost. The service will send message to mobile phones.
3.    Send SMS over email. Your mobile provider have to support e-mail to SMS service. The SMS (text message) alert will be sent to specfied addresses.
4.    Pop-up window. This is a standard balloon connected to the application icon in the system tray with the message about a problem (state change).
5.    Net Send/MSG. It is a similar standard window with a message, a standard dialogue with a message on a local or remote machine.
6.    Execute program. To start an executable file or execute the script code in a language supported by Windows Scripting Host. The path to the file and program/script arguments should be specified. You can specify user account to run the program.
7.    Send Jabber message.
8.    Send ICQ message. You should have ICQ account to use the alert.
9.    Send AOL message. You should have AOL messenger account to use the alert.
10.    Play Sound. You can use any mp3 or wav sound files. Sound will be played if Windows client application are started or Alerts tab in Web interface is open.
11.    Set SNMP value. For example, you can change router configuration with SNMP set command using thisSNMP alert.
12.    Execute script over SSH. You can start shell script on a remote computer.
13.    Send HTTP(S) request. The alert sends GET/POST request via HTTP(S) protocol to the server with specified URL. Variables can be used in the GET/POST data.
You can create a named alert using simple actions listed above and time schedules. For example, you can create an alert that contains an e-mail message to notify your system administrators and HTTP(S) request to specified Web server to submit a ticket automatically. This named alert can be used in several alerting rules assigned to various monitors. If, for example, another recipient should be added to the e-mail notification list, you can modify this named alert only, and all the alerting rules that use this alert will be immediately affected.
The full list of named alerts is available to view and edit. To open the form with alert list please select ‘Settings…’ from ‘Tools’ menu (or ‘Settings’ button on the toolbar) then select Alerts tab. It is important to remember that changes in an alert affect each Alerting Rule that uses this alert.
Alerting Rule: Whom and When To Notify
An alerting rule specifies what to do when a monitor changes its state or an event takes place. I.e., each alerting rule is a reusable template that tells the monitoring service how to respond on monitor state changes and events. In order to get a notification on a resource state change an alerting rule should be assigned to the resource monitor. Each new monitor inherits the alerting rule from its parent host by default, hence there is no need to specify a rule for each monitor separately. However, it is possible to set a custom rule for any monitor, host, host group or remote network agent. An Alerting Rule links alerts to monitor state changes.

By default, a monitor uses the Alerting Rule inherited from its parent host.
You can test an alerting rule assigned to a monitor on the special Testing tab: just click the Test button near the Alert description and check if all its simple actions are executed as expected. Make sure you will be promptly notified in case of a real-life problem occurs in your network.

Reporting Features
Here you can find the list of report types available in IPHost Network Monitor with brief descriptions.
Network Monitoring System Reports
IPHost Network Monitor provides various group and detailed reports and graphs, as well as logs. Themonitoring system reports contain information necessary to trace resource utilization trends and to plan upgrades; besides, reports and logs provide the possibility to trace the results over a certain time period. Also, the reports can be used as an accounting basis for the administrators’ work results.
There are two ways to access monitoring reports in IPHost Network Monitor:
1. Reports in Windows interface
The Windows UI (monitoring client) allows you to access detailed reports for monitors and summary reports for groups and categories. A reporting period can be any number of days and hours until now. The default report interval is 24 hours (one day) until current time. To adjust the report interval for the Windows UI select the Tools -> Settings menu or click the Settings button on the toolbar, then select the Reporting tab and set the required number of days and hours.
2. Reports in Web interface
Apart from the Windows client UI, IPHost Network Monitor also has a Web interface. Its Reports tab allows to access additional types/forms of reports for any time interval. There are three panels: the contents of the left panel completely duplicates the monitoring client Tree View pane, the upper panel serves to select the report type and time interval, the remaining space is reserved to display a report itself. The Web interface copies the monitoring client behaviour: if a link within a report is clicked, then the report corresponding to this link is loaded, and the focus switches to the corresponding tree node (agent, host group, host or monitor) in the Tree View.

Report Types
The IPHost Network Monitor provides four report types.
Summary report for a host group, host, monitor type or the entire system

This report provides summary data on the availability and performance for a selected group of monitors, host monitors, all the monitors of a selected monitor type or for the entire system. The pseudograph shows when a given monitor was in problem states. A summary report for a Remote Network Agent summarize the problems for all hosts and resources in the remote network segment and is useful to analyze and resolve them.

Summary report for a monitor
Although it has the same name it significantly differs in contents. The report presents detailed and practically complete information on the monitor’s availability and performance over a period of time.

It contains a Performance Graph, summary data on the monitor’s availability and performance (for a selected period and a previous period of the same duration), a states log (showing the state of the monitor during a selected period) and states summary information (showing how much time the monitor was in problem states and the percentage of the problem state time). For example, a traffic monitor performance graph shows how incoming traffic volume is distributed in time and can help you to optimize traffic-consuming processes on a given host.
Trend report
The report provides comparative data on a monitor availability and performance. For each monitor you can see summary data for a selected period, for a previous period of the same duration and the difference between them. You can use this report to identify short or long-term trends in the monitors’ performance and availability.

It is useful to make sure the resource performance does not degrade in course of time. For example, atraffic speed monitor trend report might show that a host or subnet network utilization should be optimized due to daily increasing bandwidth consumption.
Problem report
Shows summary information on availability and performance problems occurred during a specified time interval.

This kind of report is intended to draw you attention to the problems the monitoring service detected in your environment and to help you to resolve them. For example, repeating problems in a subnet network performance may indicate hostile activity, like a malware attack.
Log
The log shows two kinds of messages for selected monitors:
1.    system messages (not monitor specific, shown in gray font);
2.    state changes and actions (the line is highlighted in the color corresponding to a state).
The messages in the log are ordered chronologically. The Web interface Report tab allows to select logs order by clicking on Order button on the upper panel.

You can configure sending reports for other entities (agent, host group, monitor type, host or monitor) on the entity Main Parameters tab in the monitoring client.
IPHost Network Monitor interfaces and structure
Here you can find an overview of IPHost Network Monitor components, Windows and web interfaces.
Monitoring system user interface
IPHost Network Monitor user interface consists of two parts:
A monitoring client (Windows UI) allows you to view and change the monitoring system configuration and to view reports, graphs, and logs.
A Web interface (Web UI) allows you to view the monitoring resources current state or reports and graphs that show monitoring results for any time interval from any web-enabled device (i.e. from any device with web-browser).
GUI Client overview
The IPHost Network Monitor Windows interface (also called a client GUI) allows you to start, stop and configure network monitoring, obtain and analyze the monitoring results and state change notifications.
The IPHost Network Monitor client GUI displays all monitoring configuration controls, availability andperformance monitoring results and logs on one screen. This design is intended to save your time. Typically when you change the settings you expect to see the effect of your change in monitoring results, and when you see a problem in monitoring results you may want to adjust the monitoring settings or actions.
The GUI contains three view panes and a standard Windows menu, toolbar and status bar. 

Windows GUI consists of three panes:
Tree View Pane
Parameters/Results Pane
Logs Pane
Client GUI creates an icon in the system tray; even when you close the GUI main window, the icon remains present and you can double click it to reopen the client GUI. When a monitoring service is running, the icon displays the worst monitor state in your system; when the monitoring service is stopped, the icon is grayed. By placing the mouse pointer over the tray icon you can get a state summary tooltip for your monitoring system.

When the client GUI runs in the system tray, important system events such as monitoring service start and stop are signalled with tray balloons. If you set up a Pop-up window alert for a monitor, it also shows a balloon in the tray.

Tree View Pane
The Tree View pane provides various views of monitored objects and allows you to take a quick glance at the monitoring system status. By default Tree View pane opens with By Host tree. The drop-down menu allows you to switch to By Monitor Type, By State, Discovered and Favorites Views.

Each tree node contains an icon corresponding to the worst child monitor state within the node. Changing the focus in Tree View reloads the contents of all the other client panes. The frequently used actions are available from Tree View pane context menu that appears when you right-click a selected monitor or group.

Parameters/Results Pane
Parameters/Results pane is used to configure monitoring. It displays all parameters of a currently selected object. The monitor name, comment, polling frequency and monitor-specific parameters, availability settings such as timeout, monitor performance levels settings, and actions to be performed on state changes can be configured on Parameters/Results pane tabs: Main parameters tab, State conditions tab and Alerting tab.
For monitor groups, the pane also displays a monitors state summary across the group.

IPHost Network Monitor provides interfaces to several admin tools that help you to manage your hosts (servers) from the GUI client.  You can configure the interfaces on Settings -> Admin Toolspage. There are:
1.    Remote Desktop client
2.    SSH client
3.    Telnet client
You can also specify an URL for a device web interface on the host Main parameters tab.
Report Tab
Report tab displays an HTML report for a currently selected monitor or group. When a monitor is selected, a detailed report including a monitor performance graph and all the monitor state changes is displayed. The default report period is the last 24 hours and can be changed in Settings dialogue (Tools menu). When a monitor group is selected, a summary report for it is displayed. You can navigate the reports using the Backand Forward buttons on the toolbar in Report View, Refresh a report, and open the IPHost Web interface with this report loaded using the Open in browser button. When you navigate the HTML links in a report or use theBack / Forward buttons, not only the Report View content is changed to display data for the new monitor or group but all the other panes are updated too.

Logs Pane
Logs pane provides access to log messages stored in the monitoring database. You can configure it to display either system messages or monitor state change messages or both types. The state changes and events records are filtered in accordance with currently selected monitor or group; only the messages related to the current selection are shown. Host and monitor log records contain hyperlinks; by clicking on them you select a corresponding object in the Tree View pane and all the other panes.

Web interface overview
IPHost Network Monitor contains a Web interface that provides access to monitoring reports. The interface is provided by Apache web server, version 2.4.16.
The general Web interface main window layout is shown below: the Dashboard tab shows your monitoring system overview.

The Web interface provides several views of statistical data and allows you to:
quickly review the current and all previous states of your network resources
get a list of problems that have been occurred over a specified time interval
study trends and detect performance degradation immediately
generate detailed reports that include a useful monitor performance graph and detailed resource state changes log
You can choose various groups of monitors on the Reports tab to build a report; you can also choose any timeframe as well as one of the several predefined time intervals such as Today or Last week.
The Web interface Reports tab shows various configurable status reports:

There is a Tree View on the Reports tab left side. It is separated from the Parameters panel and Report panel by a vertical splitter which you can drag to resize the panels. The Parameters panel is at the top of the window and is separated from the Report panel by a grey non-movable horizontal line.
The Tree View contents match the contents of Tree View in the client application (Windows UI). There is a an accordion control to select a view (you can select View by hosts, View by monitor type, View by state,Discovered or Favorites ). Once the selected tree is loaded, you can navigate through it and highlight the necessary monitor or resource group; your selection becomes prominent in bold type. The report gets generated when you select a tree node and after you press the Generate button on the Parameters panel.
The Parameters panel allows you to select:
1.    the report type (from the drop-down menu).
There are four report types: Summary, Problems, Trends and Logs. A summary report for a monitor contains a monitor performance graph and state change log; all other reports include «pseudo graphs» (color-coded state change records) and a statistical summary.
2.    the report period. There are several predefined time intervals that you can select from the drop-down menu; once you do so, the system will set the report start and end dates automatically. You can also define the start and end dates of a report manually; the report interval will be reset to Custom. Dates are selected using a calendar, and times are chosen from the drop-down menu with a 30-minute accuracy.
When the report is configured, you can either “Generate” (the report will appear in the Report panel) or “Print” it (the report will appear in a new browser window or tab without the Tree View and Parameterspanel, and the standard Printer selection dialogue will be shown to allow printing). You can also “Send”the report over E-mail (a form will appear where the destination address and the message subject can be changed; by default, the report is sent to the administrator e-mail address).
Following the hyperlinks in reports shown in the Web interface reloads the whole interface with a corresponding tree node, type of report, and report interval already selected. You can share these links with your colleagues who might want look at the report in question. You can also open this link in a new browser window or tab to create a copy of the Web interface that already displays the necessary report. In contrast, navigating the Tree View and changing the report parameters does not reload the Web interface; only theReport panel gets updated when you press the “Generate” button.