SysOrb 4.2 released

Date:08-01-2015 We are happy to announce the release of SysOrb 4.2, which is the latest new major version of SysOrb. The main changes and new features of this release are:

RESTful API for SysOrb:
From SysOrb 4.2 a RESTful API is shipped with SysOrb server. The new API will open up for much easier integration with third party software applications and give developers the option to use SysOrb data in other applications. The new API is available for both Windows and Linux platform. Documentation on how to use the API is available in the SysOrb administrator manual.

Rescan directly from the SysOrb agent:
It is now possible to initiate a rescan directly from the SysOrb agent. On Windows this can be done via the SysOrb configuration tool and on Linux based systems it is done via init-script. This function will make it easier and faster for the system administrator to do rescan of the SysOrb agent when he is already logged on a server and doing work.

New report functions:

  • In incident report it is now possible in the formatting option to exclude nodes that did not have any incidents in the analyzed time period.
  • In the Incidents report and the system availability report it is now possible to select a precise time span to analyze. This is done via the selector in the web interface.
  • In system availability report it is now possible to include a continuous uptime graph in the report. This is done in the formatting. If any thresholds have been added to the system uptime check it will be visible on the continuous uptime graph. This will in some situations help to understand the system uptime availability calculation better.
  • In the current configuration report it is now possible to exclude check configuration, nodeclass info and checks. This gives the user the option to generate a more narrow and easy to understand report
  • Analyzed intervals are now visible in the header of a report.
    When a report is configured to only analyze data for specific weekly intervals, then that fact is now visible for the user in the header of the generated reports. This will improve understanding of the generated reports.

New Logcheck rule
The log check rule system has been extended so that "moveto" and "copyto" actions no longer only works with forward log checks as destinations, but also can be given alert groups as destinations. This can be used in situations where a user would like to be notified of every single event in a log but do not want it to be treated as an alert in SysOrb.

Platform Deprecation
With the release of SysOrb 4.2, the supported platform for the SysOrb Server has changed.
Some old platforms have been discarded and some new has been added.
Please refer to the full list of supported!.

Download SysOrb 4.2 here!

How to upgrade from SysOrb 4.0 to SysOrb 4.2

Before upgrading to SysOrb 4.2 make sure to have a up-to-date backup of your current SysOrb database. For how to backup your SysOrb database please read here! This will ensure that you can always roll back to SysOrb 4.0.

Customers using our rental based licensing model do not have to update the license key as it is already ready for SysOrb 4.2. The upgrade is done just as you would do when updating the SysOrb server to a new build. If in doubt please contact

If you do not use our rental based model you need to have a valid Upgrade & Support subscription, and you can proceed to your “My Account” and download your updated 4.2 license key.

The upgrade is done just as you would do when updating the SysOrb server to a new build. The only thing you need to remember is to replace the new 4.2 license with the existing 4.0 sysorb.lic If in doubt please contact

If you do not have a valid U&S subscription, and would like to upgrade to 4.2, please let us know at