This is a major update release, with multiple interface improvements, new features introduced, and bugs fixed.

Licensing: The Trial and Freeware Versions – from now on, there’s no separate freeware version of IPHost Network Monitor. When installed, IPHost Network Monitor enters a 30-day trial period, with a 500 active monitor limit. After the trial period ends, the Trial license is automatically converted to Freeware. The Freeware version is limited to 50 active monitors and never expires.

The Basic 200 license
We have upgraded Basic 100 license — it is now Basic 200 and supports up to 200 active monitors.

Alerting: alerting has been redesigned.

• Simple actions with a name assigned such as «Send mail» can be created. Simple actions can be reused by multiple alerts.
• Alerts can now be composed of a number of simple actions, every one with its optional schedule.
  Alerts can be named.
• Alert rules can now be tested (using the Testing tab on the monitors’ Alerting tabs). An alerting rule is executed unconditionally when tested, testing doesn’t alter the monitor state and produces log records that can be used to debug alerts.
• A new type of alert («Send HTTP(S) request») has been added, allowing sending a HTTP(S) GET/POST request on a monitor event.

Spike Filtering Redesigned
Spike filters, up to this version, allowed ignoring a single attempt to enter a problem state (Warning or Down).

The whole concept of spike filters has been changed in the following manner:

Per section spike filters can be set (every event that can cause a switch to a problem state can have its own spike filter). For example: a WMI CPU monitor can change state due to Value bounds or Response timeout. Each of these sections, as per state, can have its own spike filter.
A common spike filter can be set on the State condition tab: it will be used when none of the section spike filters can be applied (for example, if a host domain name can’t be resolved, or a connection error happens).
Spike filters can skip more than 1 attempt to change state, this counter is configurable individually per filter.
A spike polling interval can be set for every spike filter: when a spike filter is engaged, that polling interval (defaults to the monitor’s polling interval) is used.

You can find more about the release in Release Notes.