SysOrb 4.6.1 update

Date:13-06-2017: An update to SysOrb 4.6 has been released. Issues fixed are:

• Fixed: Issue in SysOrb ESXi module that in some specific network situations could result in a SysOrb crash
• Fixed: Issue in Sysorb alert module that in some specific situations could result in a crash
• Fixed: Issue in Sysorb alarm module that in some rarer situations could result in a crash

Download SysOrb 4.6.1 here!

SysOrb 4.6.0 released

Date:03-04-2017 We are happy to announce the release of SysOrb 4.6, which is the latest new major version of SysOrb. The main changes and new features of this release are:

New Feature: Agent block list:
In some situations it is not possible for a system administrator to stop SysOrb agents from keep trying to check in to the SysOrb server e.g. because the admin do not have access to a server anymore. It is now possible to block these unwanted agents. In setup new nodes list the Decline button has been changed to Block. If an admin chose to block a node it will appear under a new list called blocked nodes.

Improvements and bug fixes:

• Fixed: SysOrb server now installs correctly both on Debian7 and Debian8
• Fixed: SysOrb server now installs correctly both on RHEL6/CentOS6 and RHEL7/CentOS7
• Fixed: SysOrb server now installs on Solaris11 x86_64
• Fixed: export/import utility fails if check name contains double quote
• Fixed: in some situation ESXi check could stops updating data after certain event
• Fixed: in some specific situations Satellite synchronization could fail
• Fixed: in some specific situations error/warning events from Windows Eventlog was not shown in alert list

• Note: On UNIX systems autoupgrade have been moved to a new path /var/lib/sysorb/upgrade
• Note:On Windows systems server/agent installation is done "per Machine" to standard location
  C:\Program Files\SysOrb Server (or C:\Program Files\SysOrb Agent)
• Note:In this release we moved the SysOrb code to a new software build system Jenkins CI and and a new version control System (GIT)
  We also removed parts of legacy code and outdated target platforms. Support of the most recent compilers (C++11/14) now allows writing compact and clean code. This support the goal for SysOrb code which is to follow agile model of development.

Download SysOrb 4.6 here!

How to upgrade from SysOrb 4.4 to SysOrb 4.6

Before upgrading to SysOrb 4.6 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.4.

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

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.6 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.6 license with the existing 4.4 sysorb.lic If in doubt please contact our support.

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

SysOrb 4.4.0 update build 5749 released

Date:21-12-2015: An update to SysOrb 4.4.0 has been released. Issues fixed since build 5737 are:

• Fixed: Issue only related to ESXi datastore checks: if thresholds were violated on ESXi datastore checks the alerts would not appear on the alert list.
• Fixed: When doing rescan on ESXi servers some checks deep in the tree structure were deleted.
• Fixed: SysOrb server could crash when connection breaks and restores during a esxi-server rescan.
• Fixed: Agent would crash if admin requested downtime using command line --down parameter without '--comment' parameter.
• Fixed: SysOrb Server will now not be able to accept results from an agent that runs on a server where local server time is in the future.
• Fixed: On some database configurations if user created LogCheck rule with moveto @’name_of_your_group'; user would get at HTTP 502.2 error.

Download SysOrb 4.4 here!

SysOrb 4.4.0 update build 5737 released

Date:06-11-2015: An update to SysOrb 4.4.0 has been released. Issues fixed since build 5734 are::

• Fixed: An Issue related to SysOrb agent log checks. When operating system removed old log records to free up new space SysOrb agent would see it as a log rotation and therefore start looking through event log once again. The result was that old event log alerts would be send out again. The issue would appear on heavy loaded Windows servers, which generates many event logs.

Download SysOrb 4.4 here!

SysOrb 4.4.0 update build 5734 released

Date:04-11-2015: An update to SysOrb 4.4.0 has been released. Issues fixed since build 5732 are::

• Hotfix: An issue that was introduced in SysOrb 4.4. If the thresholds was violated on agent checks with warn or alert "when below" configured the alerts would not appear on the alert list, and emails was not send out. This issue has now been resolved.

Download SysOrb 4.4 here!

SysOrb 4.4.0 released

Date:29-10-15: We are happy to announce the release of SysOrb 4.4, which is the latest new major version of SysOrb. The main changes and new features of this release are:

Option to disable Warnings and Alerts for all types of Netchecks
This feature is useful in a situation where the only purpose of a HTTP check is to do performance measurements of website and collect the historical data for the response time.This feature also makes it possible to setup a ping check without alert threshold and therefore only receive warnings.

Support for Applications and Service Logs in Windows
This feature expand the use of the already unique log monitoring feature in SysOrb.
Administrator will now see all the Applications and Service logs in SysOrb and can easy setup monitoring of these logs.

Support for new systemd logs on Linux
Sysorb now support monitoring of journald that is a component of a new systemd init module.
Journald is a new logging scheme that works on modern Linux OS.
Journald captures Syslog messages, Kernel log messages, boot messages, messages written to STDOUT / STDERR of all services.

Easy set unexpected downtimes on multiple nodes from the webinterface
It is now possible to easy set unexpected downtown on multiple nodes at the same time.
In a situation where the administrator suddenly need to set downtime on multiple specific nodes in a domain, this feature will save the administrator a lot of time. A new button in the configuration mode called downtime
will be visible.

Flexible monthly recurrent schedule downtime function
It is now possible to set permanent scheduled downtime on e.g. every second Wednesday of the month at a certain specific time. It is also possible to choose to set scheduled downtime on certain days each month at a certain specific time. You can even choose to set a certain amount of days delay for when the downtime should start.
This feature makes it easy to configure and set scheduled downtime relative to e.g. Microsoft patch releases
The feature Monthly intervals can be found same place where you set scheduled downtime.
The feature works on both single checks, nodes, domains and from Nodeclasses.

Option to choose create shortcuts for all users in SysOrb agent installation wizard on Windows
When installing the SysOrb agent the program shortcuts etc. are per default not placed under All Users but only for the user installing the SysOrb agent. This means that only the user who installed the agent have access to e.g. the shortcut "Agent Downtime”. An option has now been added in the windows installer to choose create shortcuts for all users.

Better information on checks in downtime
If a check is set in downtime SysOrb will now in the comment field show both information “Down until” and information about the status of the check like e.g. “Too late answer”. In the status field, the actual status of the check will be readable. This will give the administrator better information on checks in downtime.

ESXi monitoring of SAN attached datastores
When monitoring ESXi host the SAN attached datastores is an important parameter and SysOrb now also support monitoring of these counters. Better translation of the some ESXi counters has also been fixed instead of only showing a number we now present a readable name for the counter.
All together, this will make the SysOrb ESXi monitoring feature even more useful for the system administrator.

SysOrb notifier Chrome extension
SysOrb notifier is a Chrome extension that can be used to get notice and status about alert and warning from SysOrb. The extension will be displayed as a small icon in your browser. In order for the notifier to work SysOrb API must be enabled. Download and install SysOrb notifier from chrome web store. Search for SysOrb in the Chrome store. Here you will also find additional information about this tool.

Improvements:

Better overview in node Incident log
When a node or a domain is set into downtime SysOrb will no longer log every single check as entering downtime. This improvement will improve the overview of the incident log as the number of log incident will be reduced.

Limit on the number of agents that can auto-upgrade concurrently
This means that for SysOrb installations with a large number of agents the SysOrb server is no longer heavy loaded during the agent auto upgrading process. Only a certain amount of agents are allowed to upgrade at the same time.

Limit on the number of concurrent agent rescan
This means that the SysOrb server will no longer be heavy loaded if you install many new agents within a short time frame. Only a certain amount of agents are allowed to rescan at the same time.

Left sidebar menu in SysOrb will now stay fixed when scrolling in SysOrb webinterface
This will make it faster and easier to navigate around between the different menus in SysOrb.

When requesting downtime from agent itself it is now possible to add a comment.

The Alert list will now automatically auto size in the browser.
When using a widescreen to display the alert list SysOrb will now utilize the extra space there is.This will give a better overview.

Increased data limit for text in the comment field for nodes and checks.
It is now possible to add more characters in comments field on both nodes and checks.

Comments on a single check are now also visible in the html emails send out from SysOrb

Extend return value for boolean Custom Check
It is now possible to return string description for boolean checks defined by result_pattern parameter of the custom check.

In license report "Satellites count" line in subdomains has been removed.
Now license report only show number of satellites for the entire root domain.

Download SysOrb 4.4 here!

How to upgrade from SysOrb 4.2 to SysOrb 4.4

Before upgrading to SysOrb 4.4 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.2.

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

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.4 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.4 license with the existing 4.2 sysorb.lic If in doubt please contact our support.

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

SysOrb 4.2.0 update build 5684 released

Date:20-05-2015:An update to SysOrb 4.2.0 has been released. Issues fixed since build 5651 are:

• Fixed: Adding a subdomain to a domain with scheduled downtime will no longer result in an error message.
• Fixed: SysOrb now accept the use of “&” in the comment field on the node.
• Fixed: SysOrb now support newest openssl libraries for linux.
• Fixed: An issue in SysOrb ESXi module that in some specific situations could result in a SysOrb crash.
• Fixed: Nodeclass autoassign now correctly detect Windows 2012 server.
• Fixed: sysorb-tool commandline help text updated.
• Improved: SysOrb agent now start hard disk scan from letter 'A'.
• Improved: SysOrb server support of SNI to ssl sockets.
• Improved: minor improvement to the SysOrb API

Download SysOrb 4.2 here!

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 platforms.here!.

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 our support.

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 our support.

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

SysOrb 4.0.0 update build 5636 released

Date:06-11-2014:An update to SysOrb 4.0.0 has been released. Issues fixed since build 5562 are:

• Fixed: Remedy property is now translated correctly to NodeClass Check
• Fixed: Downtime Node button is now removed from Alert list as it was introduced there by mistake
• Fixed: SysOrb import tool now import statistics data correct.
• Fixed: A issue where SysOrb did not start up correct in passive mode
• Fixed: A bug introduced in last build where the release key in SysOrb webinterface did not work as intended.
• Fixed: A issue where SysOrb server was logging a lot of messages, that look like debug info even though log_nodeclass_debug was not enabled
• Fixed: A issue where SysOrb server in some situations could crash if a ESXi host was rebooted while SysOrb was monitoring the ESXi host
• Fixed: A issue where HTTPS checks in some situations consistently reported "Bad reply". This issue was only present on SysOrb installations running on Linux
• Fixed: SysOrb server no longer reset server_port to default after upgrade

Download SysOrb 4.0 here!

SysOrb 4.0.0 update build 5562 released

Date:10-04-2014:An update to SysOrb 4.0.0 has been released. Issues fixed since build 5451 are:

• Fixed:log_netcheck_debug on the fly now work as intended
• Fixed:a bug that made it possible to move a node from domain A to domain B even thought a node with exact same name already existed in domain B
• Fixed: Adding NodeClass to multiple nodes via mark function could in some circumstances cause drops of other NodeClasses
• Fixed: It is now possible for a user with the only right being "Downtime, acknowledge and reset scores" to set the entire node in downtime
• Fixed: Incident report now only included alert incidents which is inside the defined time span
• Improvement: limits for dbms_cache_size, dbms_buffer_blocks and dbms_cache_size was increased
• Improvement: When adding a new node, its "Alert Group" dropdown box now default to "As Domain" instead of "As None".

Download SysOrb 4.0 here!

SysOrb 4.0.0 update build 5451 released

Date:10-10-2013:An update to SysOrb 4.0.0 has been released. Issues fixed since build 5411 are::

• Fixed: If ESXi scan fail it will now be showed in the incident log
• Fixed: Bug in the alarm module that in some rare circumstances could cause a SysOrb server crash
• Fixed: Bug when creating a moveto in a forwarded log check it would result in no changes to the logcheck.
• Fixed: In some rare circumstances Nodeclass defined NetChecks was not added automatically to nodes
• Fixed: SysOrb-tool reset scores now work as intended
• Fixed: SysOrb audit logging now work with “new line” (\ n) in comments
• Fixed: DBMS audit logging now include domain name, when putting a domain in downtime
• Fixed: SysOrb now auto configure IIS8 during installation
• Added: Option to set "agent checkin delay" in server configuration. It is now possible for the user to define how much time the agent should have before SysOrb give an alert on "late for checkin" read more about this option here

Download SysOrb 4.0 here!

SysOrb 4.0.0 update build 5411 released

Date:26-06-2013: An update to SysOrb 4.0.0 has been released. Issues fixed since build 5385 are:

• Fixed: When trying to edit and update an already existing report, you would get an error message in the web interface
• Fixed: When using custom period on a graph you would get error message: “Exception caught”
• Fixed: When remedy was running, alerts won’t be shown in alert listing for root domain during remedy downtime.
• Fixed: When remedy was running the remedy icon would overrule the alert icon in the domain tree overview for root domain.
• Fixed: Zooming in on a graph and then clicking left/right would result in an error message
• Fixed: Using alert paths during remedy state could in some circumstances cause a SysOrb server crash
• Fixed: Bug in the alarm module that could cause a SysOrb server crash
• Fixed: Init script for sles11 packages
• Fixed: Bug in SysOrb satellite that could cause the satellite to crash when updating it from 3.8 to 4.0

Download SysOrb 4.0 here!

SysOrb 4.0 released

Date:21-12-2012: Dear Customer and SysOrb user, we are happy to announce the release of SysOrb 4.0, which is the latest new major version of SysOrb.The main changes and new features of this release are:

SysOrb monitoring of VMware ESXi via vSphere Hypervisor API:
SysOrb now supports monitoring of health and performance status of VMware ESXi hosts.

• Monitor the health and performance of the physical hardware where the host runs.
• Troubleshoot problems in the virtual environment before they happen.
• Easy setup and configure thresholds for alarms and have them sent via email, SMS or script.
• All data is instantly viewable in high resolution SysOrb graphs giving you a unique overview of your virtual environment.

SysOrb uses vSphere Hypervisor APIs to collect the critical metrics for the host as well as the individual VMs. Therefore no SysOrb agents are required in order to use this feature. However for deep monitoring of the OS and applications running on each single virtual instance it is still highly recommend to use SysOrb agents.

See a video tutorial on how to start SysOrb VMware ESXi host monitoring here!

Configuration of automated actions – Remedy:
Remedy is a functionality that makes it possible for SysOrb to automatically carry out an already configured agent action. A typical situation where remedy is used could be to automatically restart a web server if it stops responding correctly. This feature will improve possible downtime in many situations and automate many of the IT administrators task. Basically, once a predefined threshold is reached, you can have Sysorb to automatically execute any script from the agent. This makes this feature very flexible.

SysOrb now ships with some basic predefined nodeclass checks:
The SysOrb server now includes some best practice checks for monitoring various operations systems and applications. This means that when a new user installs SysOrb for the first time the user will very fast have a basic monitoring setup. Just click auto assign in the web interface and SysOrb will apply basic best practice monitoring checks. This will not affect existing customers who has already a customized nodeclass configuration.

Download SysOrb 4.0 here!

How to upgrade from SysOrb 3.8 to SysOrb 4.0

Before upgrading to SysOrb 4.0 make sure to have a up-to-date backup of your current SysOrb database as it is not possible to run a SysOrb 4.0 database on a SysOrb 3.8 version. For how to backup your SysOrb database please read here! This will ensure that you can always roll back to SysOrb 3.8.

Note:Existing customers with a very big SysOrb database upgrading from 3.8 to 4.0 will experience that it might take some time before the upgrade is finished and SysOrb server is up and running. The reason for this is that we did some database changes in SysOrb 4.0. The upgrade time depends on how many nodes and checks is currently in the existing database and the performance of the underlying server setup that SysOrb runs on. In our test lab we did a upgrade from 3.8 to 4.0 with a very big database containing a main.odb file of 11 GB and it took approximately one hour before the upgrade was complete.

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

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.0 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.0 license with the existing 3.8 sysorb.lic If in doubt please contact our support

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

SysOrb 3.8.0 update build 5316 released

Date:06-09-2012: An update to SysOrb 3.8.0 has been released. Issues fixed since build 5204 are:

• Use of log check rule ”moveto” could in some cases cause an error in the web interface
• Several improvements to the documentation (administrator’s guide)
• sysorb-tool can now reset scores, set downtime and list available actions for a node
• Centralized audit logging introduced; certain events can be logged to the server log for auditing
• The SysOrb agent will now handle up to 65536 network interfaces on a node; useful for linux routers with many VLANs configured
• Fixed a metric extraction problem in sysorb-tool so that the database tuning knowledge base article once again is accurate
• Fixed FTP NetCheck compatibility problem against the Windows 2000 SP4 FTP service (version 5.0)
• Fixed a network related bug that could cause ICMP checks to cease executing on Windows based SysOrb servers

Download SysOrb 3.8 here!

SysOrb 3.8.0 update build 5204 released

Date:26-01-2012: An update to SysOrb 3.8.0 has been released. Issues fixed since build 5183 are:

• Fixed: Resolved a rare problem in DNS lookup code
• Fixed: Fixed a rare problem on Windows 2008, where the DNS resolver could hang, causing checks to fail
• Fixed: In specific situations, SysOrb would not handle broken SNMP packaged elegant, and would consume a lot of CPU.
• Fixed: In some situations Sysorb would send a normal ICMP request followed by corrupt IP packages which in some situations resulted in false alarms
• Improved: On the sysorb server it is now possible to enable extra debug logging on the fly. This means that in support cases where extra logging is needed it is no longer necessary to restart the sysorb service in order to get the extra logging.

Download SysOrb 3.8 here!

SysOrb 3.8.0 update build 5183 released

Date:11-11-2011: An update to SysOrb 3.8.0 has been released. Issues fixed since build 5157 are:

• Fixed: Netcheck frequency that were occasionally off under special circumstances
• Fixed: Incident log does not allow next page if all entries have same timestamp.
• Fixed: Wrong alert group selection in domain. It is no longer possible to choose unavailable alert groups in domain.
• Fixed: A handle leak in sysorb-netcheck which resulted in growing CPU utilization on the sysorb server
• Fixed: Broken links to online documentation from the Quick Links menu.
• Fixed: Prevent web interface refresh on current page, when a link has been activated
• Fixed: Web interface error when viewing Alert List from Other Views.
• Fixed: Virtual memory and page file check was wrong on some versions of Windows
• Fixed: Memory leak in sysorb-remcheck and sysorb-icmp
• Fixed: Crash in sysorb-alert process in some situations, when ordering unexpected downtime.
• Improved: The sysorb-tool utility can now properly update inherited properties

Download SysOrb 3.8 here!

SysOrb 3.8.0 update build 5157 released

An update to SysOrb 3.8.0 has been released. Issues fixed since build 5153 are:

• An issue with nationalized performance counter names was introduced in 3.8 that could prevent performance counters from being checked on some nationalized windows configurations. This has now been resolved
• A spurious network communication problem that only could occur on Windows platforms and seems to have only happened on 64-bit Windows platforms, has been fixed. This problem could cause the web interface to fail displaying large pages (like large alert lists) for example.

SysOrb 3.8.0 released

Date:30-09-2011: Dear Customer and SysOrb user, we are happy to announce the release of SysOrb 3.8, which is the latest new major version of SysOrb.The main changes and new features of this release are:

• Ability to set alert group for an entire domain:
  Now the administrator no longer needs to set alert group on each individual node but can set an alert group for an entire domain. This feature will ease the configuration of SysOrb significantly and save a lot of time when configuring new domains and nodes.
• In graphical view, it is now possible to use label instead of node name:
  In SysOrb 3.6 the node name was used to display the name of the node in the graphical view. This,in some cases, caused too much text on the graphical view. Now SysOrb uses the node label instead. This also implies that if the label is empty, no name will be displayed at all. There will only be the read/yellow/green bulb - no actual node identification. This improvement will make the graphical view even more smart and useful.
• Improved IPMI sensor support:
  IPMI is the Intelligent Platform Management Interface which is an open standard that is integrated into most systems by hardware manufacturers. IPMI can provide real time hardware information such as system temperatures, voltages, fan speeds and hardware status. SysOrb already has advanced support for IPMI but we now improved the IPMI support even further. The range of different hardware types which SysOrb can monitor has therefore also been expanded dramatically, including, among other things, the server chassis LEDs.
• IO infrastructure cleanup:
  The IO infrastructure is the backbone of SysOrb. The IO infrastructure improvement speeds up and cleans up the core network and inter-process communication components of SysOrb. This allows SysOrb to process more checks, more requests and more data, faster than ever before.
• Improved NetCheck performance solution:
  The NetCheck code was not as efficient as it could be and some operations could be very CPU intensive. In SysOrb 3.8 we have re-designed the NetCheck logic so that it can perform more efficiently.
• Named devicemapper devices on Linux:
  SysOrb currently display statistics for "dm-0", "dm-1" and so forth; using the devicemapper device numbers. This was not so useful for the administrator, as he usually will be referring to the named devices (eg. vg0-swap, vg0-home,). The improvement will present the administrator with the proper logical volume names instead of the device mapper numbered devices.
• Solaris CPU status readout improvements:
  SysOrb can now present CPU statistics from Solaris systems that are similar to those presented for Linux and Windows systems. This is very useful information for the Solaris administrator.
• New Solaris 10 x86 agent:
  The Solaris 10 x86 agent has been modernized to integrate fully with the Service Management Framework (SMF) and now also has extensive ZFS support.
• Downtime comments in incident log:
  In SysOrb 3.6 you can specify a comment when setting downtime, but this comment never appears in the incident log for the node. In SysOrb 3.8 this comment is now visible in the incident log.
• Allow a comment under stations:
  It is now possible to enter a comment when editing the station info under system setup. The comment display when one views the Stations list. This is very useful information for RDP access etc. to the stations.
• Downtime notifications in node incident log:
  Whenever a domain, node or check enters or leaves downtime, a suitable record will appear in the corresponding incident log for the node.
• SNMP packet spacing option:
  An Option for packet_spacing for SNMP packet transmission has been implemented.

Download SysOrb 3.8 here!

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

  If you are not subscribed to 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 3.8 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 3.8 license with the existing 3.6 sysorb.lic If in doubt please contact our support.
  If you do not have a valid U&S subscription, and would like to upgrade to 3.8, please let us know.

SysOrb 3.6.0 update build 5145 released

Bugs and problems fixed from 3.6.0 build 5054:

• Improved log output in the agent to better assist in finding the cause of late checkins
• Fixed a web interface crash that was introduced while fixing another problem in the last update
• Fixed an agent crash when scanning a Windows host with no physical disks
• Fixed a performance problem with "View as AlertList"
• Fixed a performance issue with a large database query from the forecaster
• The capability "Create, edit and delete checks" did not allow edit or deletion.
• Improved log output to assist the administrator in finding the cause of "AlertPath no longer exists" log messages on the server
• Fixed a problem where SysOrb could continue to send alerts for a check if it was deleted while in alert state
• Fixed a server crash that could be caused by network failure at a particular time during grid synchronization
• Improved logging from the database process in case of emergency shutdown
• Fixed a problem where SMS alerts could be sent after a check had returned to OK status, if the SysOrb server was stopped after the check failed and re-started after the check was repaired
• Fixed a problem where the sysorb-alarm process would consume 100% CPU time (of a single core) if a sufficiently large downtime had been scheduled for a single check.
• The downtime selector sometimes did not work properly on the last day of the month
• Fixed a report generator crash that could be caused by report e-mail transmission failure
• SNMP tags could appear to disapper in the configuration due to a problem with the way tree structures would auto-expand in the web interface. The auto-expansion has been fixed, which should eliminate this confusion
• Fixed a web interface crash caused by attempting to display a deleted domain in the alert list

SysOrb 3.6.0 update build 5054 released

Bugs and problems fixed from 3.6.0 build 5023

• Fixed inability to clear a nodeclass override of the "Acknowledge alerts" property on a check
• Domain links in the alert list would not be usable if the domain was assigned a comment or an Information URL
• The graph plotting CGI program will now gracefully fail when it cannot connect to the server, instead of writing a core file or a crashdump
• Performance counters are now identified by their English names in order to allow node classes to function across servers of different nationality.
• Improved performance counter readout after reboot of counters that require multiple readings to produce a value
• Improved SNMP check reporting of OIDs that disappear
• Permission problem; in some situations a user could be denied access to setting downtime, even if the user was allowed to set downtime and acknowledge alerts
• Added whitespace trimming of form fields to prevent hard-to-see typing mistakes
• In some situations it was impossible to clear the override property on a logcheck
• Fixed Chrome browser compatibility problem that prevented automatic refresh after downtime had been set from the alert list
• Added reporting of the AMD64 (x64) processor architecture in the Windows agent Node Information
• Some node move operations could cause a web interface crash instead of a proper explanation as to why the operation could not be performed
• Improved logging of custom agent check sub-process exits so that the agent now logs which signal caused sub process termination (if applicable)
• Fixed a web interface crash with the error message "Assertion failed: short length given to dot_string_width"
• Fixed invalid UTF8 encoding error from the sysorb-exporter XML export tool
• Fixed handling of \r, \n and \t characters in regular expressions used in Logcheck filter rules
• Disabled the "edit node" button for users that do not have node configuration rights (this is not a security fix - configuration updates were correctly denied, but presenting the edit option is confusing for users who are not allowed to edit)
• The agent will only test for agent.conf configuration files at predetermined absolute locations - it will no longer accept an agent.conf file in the current working directory (unless the CWD is one of the predetermined paths on the given platform)

SysOrb 3.6.0 update build 5023 released

Bugs and problems fixed from 3.6.0 build 4960

• The snmp checker could stop receiving results due to network errors and never recover on Windows servers. This has now been solved.
• The handling of SIGTERM was incorrect in sysorbd on Solaris. This could cause the server to shut down when a log rotate was initiated.
• Corrected various problems in error handling that will make the system more robust and make system error reporting more reliable.
• Resolved a rare problem with transmission error handling during grid communication (satellite/master synchronization) that could cause the transmitter to crash under the right circumstances.
• Corrected error handling in the ICMP (ping) check logic that could cause a retransmission to be forgotten, causing a check to stop executing.
• Corrected manifests for 64-bit SSL DLLs that could cause problems getting SSL checks to work on 64-bit Windows servers
• During report generation, the e-mailed graphs could under some circumstances contain incorrect data; if the report was viewed in the web interface it would be correct.

SysOrb 3.6.0 update build 4960 released

December 7th, 2010: Bugs and problems fixed from 3.6.0 build 4933

• Fixed a database crash when deleting nodes (the more nodes deleted at a time the greater the risk of hitting the problem).
• Fixed a problem on Windows with SNMP probes stopping completely after a failure has occured.
• Resolved an issue with HTTPS checks not working on 32bit Windows.
• SNMP retransmit and timeout settings are now configurable.
• SysOrb could crash on reception of malformed UDP packets. This has been fixed.

Download SysOrb here.

SysOrb 3.6.0 update build 4933 released

October 8th, 2010: Bugs and problems fixed from 3.6.0 build 4903:

• In certain NodeClass configurations it was impossible to override the alert group setting for a check; this has now been fixed
• Corrected a problem with Log check rules and downtime setting overrides in NodeClass configurations
• Improved cryptographic key renegotiation in the agent to more smoothly work with systems that are abruptly powered off
• Multichecks were not previously visible in the agentchecks overview
• The server would previously cause an agent to report an error if the agent checks in with no configured checks
• Improved error handling in the web interface when invalid operations are performed and java-script is disabled

SysOrb 3.6.0 update build 4903 released

September 6th, 2010: Bugs and problems fixed from 3.6.0 build 4855:

• Resolved nodeclass conflict triggered when different servers report sensors in the same group of different types; for example when mixing IBM and Dell servers in the same nodeclass
• Resolved 'Property Tag not found' error that could occur on certain checks under rare circumstances, both when viewing and editing the checks.
• Changed navigation in log checks to improve paging through very busy logs
• Changed warning/alert restriction so that percentage limits can be used in nodeclasses and successfully applied to checks with zero capacity. Previously the alert level was required to be below the warn level, but for zero capacity checks this would cause a nodeclass conflict
• Displaying a single check in an alert-list view could fail with an error in certain configurations - this has now been resolved
• Improved windows event log parsing to deal with extra parameter substitution
• Resolved regression introduced in 4855: If a check fails, enters downtime, gets fixed and leaves downtime, it would not return to ok status before it failed again and was resolved again
• AgentActions configured in a nodeclass would trigger unconditionally
• Fixed a number of small resource leaks in the agent across all platforms
• The status icon for a check could get stuck with one of the downtime icons - this has now been fixed
• Fixed problem with adding nodes with quoted names
• Improved error handling when pager device fails
• Resolved rare crash in the time series database related to extraction of check data
• Resolved a basket problem when adding nodeclass check dependencies to a nodeclass check

Download SysOrb here!

SysOrb 3.6.0 update build 4855 released

July 26th, 2010: Bugs and problems fixed since 3.6.0 build 4838:

• Fixed a situation where alerts could be transmitted more than once although repetition was disabled.
• Fixed a bug that caused LogChecks to incorrectly display 'Rules' as being overridden.
• Fixed a bug that caused ScoreKeeper controlled checks to sometimes stay too long in Warning although the check had already changed to OK state.
• Fixed a number of minor memory leaks in the sysorb-forecast process.
• Fixed a rare crash in the sysorb-uplink process.
• Fixed a problem where adding a custom alert path could fail on new SysOrb 3.6.0 installations (installations upgraded from a previous release were unaffected).
• A problem in the agent where it could in some cases miss the first 16 bytes of log lines when parsing extremely busy logs has been fixed.
• A problem with DNS lookups and custom netchecks has been resolved.
• A problem with shutting down custom check scripts that exceed their allowed runtime has been fixed.
• A rare crash of the sysorb-alert process on Windows has been fixed.
• Fixed some memory leaks in the sysorb-dbms process.

Download SysOrb here!

SysOrb 3.6.0 update build 4838 released

May 17th, 2010: Bugs and problems fixed from 3.6.0 build 4831:

• Agent can now preempt huge log parsing to check in on time
• Fixed very rare crash in the sysorb-socketio process caused by connection failures
• Fixed crash in the sysorb-alert process related to custom alert path transmission
• The nodes in the alert lists were not always clickable - this has now been fixed
• Fixed problem with single NetChecks failing after DNS name resolution errors
• Fixed problem with all ICMP checks failing on Windows servers
• Fixed an issue that sometimes prevented acknowledge of logchecks

Download SysOrb here!

SysOrb 3.6.0 build 4831 released

April 26th, 2010: Bugs and problems fixed from 3.6.0 build 4808:

• Fixed "Every month day" configuration option in report template configuration dialogue
• Fixed crash when a grid station configuration was released while synchronizing
• Fixed problem with adding log checks in certain cases (re-adding a previously deleted check)
• Fixed problem with SSL DLLs shipped for 64-bit Windows servers (fixes HTTPS check problems)
• Fixed dialogue "hang" (depending on mouse movement) during scan for SysOrb Server in Windows based Agent installation
• Fixed "Create, edit, delete and generate reports" user capability to function precisely as documented
• Fixed "Downtime, acknowledge and reset scores" user capability to allow setting of downtime
• Fixed resource leaks in the Linux agent caused by loss of network connectivity
• Fixed sysorb-alert process (alert transmission) crash
• Fixed satellite crash caused by master restart
• Fixed event log check formatting problem introduced during the event log check improvements in build 4808
• Fixed a significant performance problem with large deletion operations (during agent rescan or node deletion for example) on Windows based SysOrb Servers
• Fixed several resource leaks in the agent on all platforms when reading discrete IPMI sensor values (drive bay status, RAID error etc.)
• The SysOrb Server now manually updates the timestamp on its database journal (main.odbj) on Windows and Linux, as these platforms do not properly track changes to this file - this makes it simpler to back up the SysOrb database, as it is no longer required to manually configure the backup program to unconditionally include the journal
• The UNIX and Linux agents no longer ship an empty variables file; this cures the potential need to release agent keys after a manual package upgrade
• Corrected name of the superuser capability ("Server" not "ServerCluster")
• The Solaris 10 agent packages now stop the service before upgrade
• Improved logging and diagnostics output for server and agent crashes on Windows based systems

Download SysOrb here!

SysOrb 3.6.0 build 4808 released

April 9th, 2010: Bugs and problems fixed from 3.6.0 build 4783:

• Fixed a grid object versioning problem that was introduced during 3.6 development; if you experience problems with agent or snmp rescans in a grid setup using 3.6, please make sure your master and satellite are running at least build 4808
• Added uninstallation support for the web interface on IIS 7
• Improved variables file handling during the issue of agent-initiated downtime (soagent --down)
• Removed need to explicitly choose "Run as administrator" on the "Set agent downtime" link on Windows 2008 and similar
• Fixed IIS 5 configuration problem during install
• Worked around a Windows Event Log problem which could cause the agent to crash
• On Linux the block device checks now finds both hd and sd devices
• Corrected the URL to our administrator and user manual downloads

Download SysOrb here!

SysOrb 3.6.0 build 4783 released

February 10th, 2010: Bugs and problems fixed from 3.6.0 build 4769:

• Reduced database CPU load on larger installations receiving many NetCheck results
• Solved a problem with improper handling of Downtime on Nodes and Checks
• Ping (ICMP) check retransmission and scheduling behaviour fixes and improvements
• In rare cases agent deletion rapidly followed by agent check-in could cause a grid master to shut down
• Significantly improved performance of a database query related to display of Alert List web pages
• Fixed log check name printing problem in configuration of Parasite Log Checks
• Solved an IIS7 compatibility issue that could cause form POST requests to fail
• In rare cases the sysorb-socketio process on Windows would shut down due to network communication errors

Download SysOrb here!

SysOrb 3.4.2 build 4782 released

February 10th, 2010: Bugs and problems fixed from 3.4.2 build 4664:

• Ping (ICMP) check retransmission and scheduling behaviour fixes and improvements
• In rare cases agent deletion rapidly followed by agent check-in could cause a grid master to shut down
• Significantly improved performance of a database query related to display of Alert List web pages
• Fixed log check name printing problem in configuration of Parasite Log Checks
• Solved an IIS7 compatibility issue that could cause form POST requests to fail
• In rare cases the sysorb-socketio process on Windows would shut down due to network communication errors

Download SysOrb here!

SysOrb 3.6.0 update build 4769 released

January 15th, 2010: Bugs and problems fixed from 3.6.0 build 4751:

• Agent Actions would repeatedly trigger - this problem has now been solved
• Several web interface errors, causing the web server to display an 'internal server error' have now been corrected
• Fixed a windows installer error that could cause an error dialog box to show up during IIS configuration
• The scheduling and retransmission handling of the ICMP (Ping) checking logic has been improved

Download SysOrb 3.6 here!

SysOrb 3.6 released

December 30th, 2009: A new major version of SysOrb has been released. The main changes and new features of this release are:

• New platform support. Support for additional newer platforms has been added including support for 64 bit platforms. Various older platforms have been deprecated.
• Graphical custom views. It is now possible to create custom graphical views in the SysOrb web interface using custom pictures (e.g. floor plans and area maps) and display the state of checks in a clear graphical manner.
• Set down time from agent. Unscheduled downtime can now be set from the agent itself easing administration of the individual server.
• New agent checks. The SysOrb agent has been upgraded to support new interfaces for checking including SAS disk status through IPMI interface and better file system statistics support on Windows and Linux.

Download SysOrb 3.6 here!

SysOrb 3.4.2 update build 4664 released

October 22nd, 2009: Bugs and problems fixed from 3.4.2 build 4648:

• Solved a Windows-specific problem with execution of Custom Alert paths
• Solved a generic problem with shutdown of broken network connections
• Solved a Windows-specific problem with error handling of UDP transmissions, as used by the SNMP stack - this problem could cause some
• SNMP checks to wrongly be reported as "unknown"
• Solved a generic problem with NetCheck scheduling on very busy systems
• Solved a generic performance issue that could cause major delays in web interface responsiveness when reverse-DNS lookups of unconfigured agent names time out or are very slow

Download SysOrb 3.4.2 here!

SysOrb 3.4.2 update build 4648 released

October 7th, 2009: Bugs and problems fixed from 3.4.2 build 4599:

• One potential problem with e-mail transmission of reports has been fixed
• A problem where some checks (SNMP and NetChecks) suddenly stopped executing has been fixed
• The content of larger e-mail alerts could in some cases be repeated inside the e-mail.

Download SysOrb 3.4.2 here!

SysOrb 3.4.2 update build 4599 released

September 15th, 2009: Bugs and problems fixed from 3.4.2 build 4593:

• The sysorb-socketio process could cause SysOrb Server shutdowns on Windows in certain situations
• Grid links would sometimes be initiated to bad port numbers on the grid peer, causing unnecessary delays in grid link establishment
• If a grid satellite and master were both configured to attempt to establish a link to the peer, a race was possible which could cause the grid logic to shut down the SysOrb Server

Download SysOrb 3.4.2 here!

SysOrb 3.4.2 released

August 31st, 2009: The main focus of SysOrb 3.4.2 has been on better accommodating larger installations. There are two main changes in this release over 3.4.1:

• A complete rewrite of the central message passing interface internally in the SysOrb Server. The end result of this is, that the server can better scale to larger setups with more agents and more SNMP devices. It also improves the scalability over multiple cores; the SysOrb Server can now better utilize multi-core servers.
• Tagging for advanced SNMP setups. It is now possible to either manually tag ports (like switch uplink ports for example) on switches and other equipment, and have the tag affect how NodeClasses are applied. The tagging can also be automatic, allowing for example the port link status check to be either enabled or disabled depending on the administrative status of the port. This allows for seamless integration of the SysOrb SNMP monitoring with vendor-provided, 3rd party or in-house SNMP device configuration management systems.

Download SysOrb 3.4.2 here!

SysOrb 3.4.1 update build 4490 released

March 26th, 2009: Bugs and problems fixed from 3.4.1 build 4333:

• The nodeclass logic could erroneously flag conflicts in certain rare cases, such as a SNMP device lacking ifInOctets or ifOutOctets in one entry in the ifTable.
• Rare crash problems fixed in the nodeclass logic, in the alarm logic and in server-side agent communication code related to Agent Actions
• Fixed problems with setting non-recurring downtime
• Added emptying of serial port data during server shutdown, to prevent kernel warnings about modem data loss
• Improved handling of broken IPMI readouts from various BMCs; this solves problems on IBM servers with failing temperature readouts on non-existing CPUs and Dell servers with non-conforming ambient-temperature sensors
• Fixed report generator error wrt. leap second handling
• Extended list of recognized operating systems on the Windows agent
• Fixed problem with small agent data-loss during server shutdown
• NodeClass configuration tree did not properly handle sub-domain users
• Log rotation on the Windows agent would leak handles
• Added quarterly reporting and recurrence to the report template configuration
• Added optional User-Agent string option to HTTP checks to allow workarounds for broken site configurations
• Updated company name and copyright information

Download SysOrb 3.4.1 here!

Evalesco på ICT / INTERNET EXPO, 13-14 Januari 2009

November 28th, 2008:
13-14 Januari 2009, Svenska Mässan Göteborg

SysOrb 3.4.1 released

February 27th, 2008: New features:

• Comments on downtime, acknowledge, reset score. The operator now has the option of assigning a textual comment to these operations.
• This comment will be included in emails sent to other users, as well as put in the Incident Log
• Ad-hoc multichecks. A powerful feature allowing the user to select a number of checks on any overview page, and have the graphs of all these checks shown in the same coordinate system.

Improvements:

• Improved support for VmWare ESX
• SNMP queries on arbitrary port
• Custom check scripts run in separate process group
• Bounded memory use on SysOrb agent

Bugfixes:

• The SysOrb agent no longer wrongly detects SCSI drives in some IBM backplanes as inactive.
• Fixed memory leak in agent.
• Ability to create SSL NetChecks using NodeClasses
• Better flow control of bulk data from satellites

Download SysOrb 3.4.1here!

SysOrb 3.4 is now available!

May 10th, 2007: New features and improvements:

• New agent platform: Debian 3.1 (and later) on 64-bit x86
• Added SSL support to relevant NetChecks (HTTPS, IMAPS, POP3S)
• Simplified the Windows package install process
• Server package for Windows now includes a simple web server for easier installation
• SmartArray support on HP Proliant servers running Windows and Linux based operating systems
• Added support for hardware/environment monitoring via. IPMI on Windows and Linux based operating systems
• MultiChecks allow for displaying multiple checks in one graph
• Significantly improved zoom support on graphs
• Improved unit presentation and number scaling in continuous graphs
• Allow publicly-editable views
• Improved usability in views editing; persistent tree browsing
• Improved grid master performance in multi-satellite setups
• Allow adding custom logos, headers and footers to reports
• Allow adding the domain path to the alert message subject
• Associate agent actions with agent checks for quick intuitive remedies presented with warnings and alerts
• Added search in the web interface, to allow easy searching for nodes, nodeclasses and domains
• Improved entry of unexpected downtime
• New view presentation functionality; view-as-alertlist and collapse
• Allow comment-fields on nodes and domains
• Allow easy display of which nodes are members of a given nodeclass
• Various web interface improvements

Download SysOrb 3.4 here!

SysOrb 3.2.2 is now available!

November 14th, 2006: New features and improvements:

• Option to display alternative units on checks, e.g. Bytes or bits, Celsius or Fahrenheit etc.
• Simplification of the installation procedure on Windows platforms
• Support for dynamic SNMP tables
• Configuration of time zone per user
• Extension of the available check types on Novell NetWare
• Zoom feature on graphs (zoom in on and display a certain period)
• Option for including the AlertPath logging in the Incident Log on the nodes
• Performance improvements and optimizations
• Usability improvements
• New OS platform: SysOrb Agent for Windows 64-bit on Intel Itanium
• New OS platform: SysOrb Agent for FreeBSD 5/6
• New OS platform: SysOrb Agent for NetWare 6

Bugs fixed in relation to 3.2.1 and earlier:

• Acknowledgement is now always enabled on LogChecks
• Bug fixes and optimizations in relation to SysOrb Satellites
• A bug that meant that SysOrb did not immediately discover changes to Alert Groups

Download SysOrb 3.2.2 here!

SysOrb 3.2.1 is now available

April 12th, 2006: New features:

• NodeClass "must-have" option, to ensure that member nodes have the specified check

Improvements:

Significant grid synchronization speedups
• Time series database performance improvements - improves performance on servers with large numbers of checks
• Improved "move node" performance
• Various small optimizations in the database query engine and the connection handler
• New index introduced in the database which significantly improves the response time on certain common queries
• Performance metering interface in the SysOrb server (accessible via. the sysorb-tool utility), to assist in performance tuning and troubleshooting

Download SysOrb 3.2.1 here!

SysOrb 3.2.1 released

April 12th, 2006: We have now released SysOrb 3.2.1, the first release of significant improvements after 3.2. Read more about the new version here!

SysOrb 3.2 update build 3353 released

December 19th, 2005: Bugs and problems fixed from 3.2 build 3341:

• SysOrb 3.2 build 3353 contains all bugfixes from SysOrb 3.0.3 up to and including build 335
• The init-script configure option now detects duplicated servers
• Improved diagnostic output of the agent configuration test utility
• SysOrb Server would not start on Debian 2.2 (Potato)
• Fixed agent auto-configure on Debian 3.0 (Woody)
• Improved reload and caching of PNG images (Internet Explorer specific)
• Fixed report selection problem (Internet Explorer specific)
• Fixed report check name sorting
• Improved usability in the Windows installer
• Improved usability of the POSIX systems agent test and configure options
• Corrected height of tabular graphs in reports
• Fixed accidental removal of the plain-text view in the web interface
• Fixed problem with sysorb-alert shutting down in certain cases involving alert path deletion
• Fixed 'acknowledge' from the alert list

Download SysOrb 3.2 here!

SysOrb 3.2 has been released

December 7th, 2005: We have now released SysOrb 3.2, the next major version after the 3.0 series. Read more about the new version here!

SysOrb 3.2 is now available

December 7th, 2005: New features:

• Support for dependencies among nodes and checks (avoiding alerts from netchecks behind a backbone router if the backbone router is down)
• More flexible notification; 'back to green' and other options
• Dynamically updated Alert View
• Server discovery support (for LANs) during agent configuration

Improvements:

• General usability and performance improvements in the web interface
• Easy configuration of new previously-nonconfigured agents in the web interface
• New graph type for discrete (eg. process presence, SAFTE enclosure disk slot status etc.) and 'uptime' type time series
• Significant re-work of the alert subsystem to improve message handling and messaging performance

Download SysOrb 3.2 here!

SysOrb 3.0.3 has been released!

July 25th, 2005: We have now released SysOrb 3.0.3, an update to 3.0. Read more about the new versionhere!

SysOrb 3.0.3 is now available!

July 25th, 2005: New features:

• Support for RAID disk enclosure monitoring on Windows and Linux
• Monitoring of per-processor statistics on Linux
• Alert if satellites loose contact with central grid server

Improvements:

• Various speed optimizations in SysOrb server
• Allow deselection of Incident logs in availability reports
• Improved HTTP NetCheck support
• Manual assignment of NodeClasses to multiple nodes at once

Bugfixes:

• Ability to put check accumulations in custom views
• SysOrb web interface crashed when viewed in some PDAs
• Problems with copying nodes which belonged to NodeClasses
• SysOrb agent gave faulty readings on 64-bit version of AIX
• Various issues with XML im-/ex-porter

Download SysOrb 3.0.3 here!

SysOrb 3.0.2 is now available!

May 11th, 2005: New features and improvements:

• Addition of options on Views - shorter text, full-screen option, and customization of graphs
• Performance improvements at database level, making the web interface react/run faster
• Improvements of the java tool-applet for launching third-party tools
• Design changes to the web interface in general

Bugs and problems fixed from 3.0.1 and earlier:

• Problems in copying and adding Cumulation checks on network interfaces
• NodeViews, acknowledgement and downtime setting did not work
• Problem in monitoring more than 2GB Memory on Windows
• Missing check boxes in the "Check conflict" screen
• Upgrade of SysOrb Server on Windows would remove settings for GSM modem
• The SNMP process could "hang" in rare cases
• The SysOrb Agent for Windows could "hang" if scanning a removable disk

Download SysOrb 3.0.2 here!

SysOrb 3.0.1 has been released!

February 14th, 2005: We have now released SysOrb 3.0.1, an update to 3.0, introducing features that are especially interesting for large installations and xSP's. Read more about the new version here!

SysOrb 3.0 is now available!

December 19th, 2004: New features and improvements:

• NodeClasses configuration - define your checks per NodeClass to easily monitor multiple similar nodes
• SysOrb Satellite, enabling you to setup a Satellite on a remote network in order for it to monitor locally and report back data to the central
• SysOrb Server - authenticated and encrypted. Ideal for xSP's or companies with multiple remote locations.
• Views based on NodeClasses - easily set up and maintain a View showing all the nodes of a certain NodeClass
• Icons for NodeClasses - also insert your own icons to supplement the default icons
• Configuration Report - new report type that lists the configuration of any combination of nodes, in order to more easily review existing configurations
• Report editing - a new option to the report generator that enables you to insert your own comments etc. to reports before you publish/send them to users
• Change log to report templates - track who changes report configurations, when reports are generated and to whom they are sent
• AlertPath log - track the usage of individual AlertPaths to see when they were used etc.
• Summary in e-mail header - in the subject line of an alert e-mail, the number of entries in the alert summary (if any) will be shown
• PDA web interface improvements - polished interface and shorter download times
• Tool applet improvements - the java applet for launching third-party tools has been improved and polished
• Option to export only NodeClasses
• Web interface improvements - more short-cut buttons, and graphical design has been polished
• General performance improvements to the SysOrb databases
• Auto-Discovery no longer automatically sets up checks on discovered nodes
• New OS platforms: SuSE 8.2/9 now supported out-of-the-box - both Server and Agent

Bugs and problems fixed from 2.6.2 build 2914 to this build:

• None

Download SysOrb 3.0 here!

New 2.6.2 build: 2808

August 17th, 2004:Build 2808 of SysOrb 2.6.2 fixes the following issues:

• Unintended monitoring server shutdown caused by certain HTML alert path configurations
• Multiple NetWare Agent fixes; log file scanning would in certain cases not find all existing log files, and the agent could in certain configurations
• cause an abend on the NetWare Server.
• The PDA mode in the web interface could revert to non-PDA mode during use
• Inability to specify percentage-based thresholds in the web interface

New version available!

July 20th, 2004: We have now released SysOrb 2.6.2 - you can click here to read more about this latest version.

New SysOrb 2.6.2 version is out!

July 20th, 2004: New features and improvements:

• AAddition of options in report configuration for min/max/no response, and display of incident log entries
• Support for uptime measurement on SNMP units and its ports/interfaces
• Option for configuring threshold values in percentages rather than in absolute numbers (eg. 20% disk space)
• QuickLinks in the web interface (for manuals on SysOrb)
• Option to add your own QuickLinks
• Increased information from SysOrb Agents on NodeClasses - in connection with an Auto-Discovery process
• Display of configured downtime in the summary and results pages for a given node - increases overview
• Addition of 30- and 45-minute intervals to Unexpected Downtime configuration
• Explanation of Availability calculation in reports
• Minor usability improvements in the web interface
• New SysOrb Agent: Tru64 (from 4.0f and on)

Bugs fixed in relation to previous releases:

• Problems in deleting intervals in Scheduled Downtime
• HTML-problems in e-mails for Unexpected Downtime
• Lack of scanning/reading of certain performance counters on local-language versions of Windows
• Inappropriate availability calculation, if a process presence check is included, and the process is not supposed to run
• At manual addition of a process in the web interface, the Agent was not properly re-scanned
• Problem with proper functioning of Custom Alert Paths on Windows
• The report type "severe events" was not displayed correctly
• Using a View with "view-in-view", the box status color did not change to yellow and red, respectively

Download SysOrb 2.6.2 here!

SysOrb 2.6.1 is now available!

March 26th, 2004: New features and improvements:

• "Silence check" on LogChecks - be alerted if e.g. a LogCheck is silent for more than 24 hours
• Forward-rule for LogChecks, so as to divide LogCheck on one log file (e.g. Event Log) into several types (e.g. per application)
• Option for displaying miniature real-time graphs in the View boxes = much improved overview
• Option to add one View to a box in another View, thereby building a hierarchy of Views
• Node Info improvements - addition of info on IP-number, MAC addresses etc.
• Support for un-attended installation of SysOrb Server and Agent on Windows platforms
• Cookie-based login in web interface - avoid having to log in when clicking on links in alert e-mails
• Certain HTML commands in the comments field on checks
• Improvement of performance during "Move Nodes" operation
• Compression of XML imports/exports
• Support for PDU format when sending SMS notifications
• Monitoring of the SNMP counter 'Uptime' with snmpChecks
• Option to add a label to SysOrb Domains
• New report type: Text-only report
• "Worst case" availability figure for Domains/Nodes/ Checks in reports

Download SysOrb 2.6.1here!

Updated build for SysOrb 2.6 is now available

March 26th, 2004: Known bugs fixed in build 2638 of SysOrb 2.6:

• When Auto-Discovering existing nodes, existing NetChecks are reset
• The fixed y-axis settings seemed to not work in some cases
• When displaying NodeViews, there were no buttons for short-cuts at the bottom
• Auto-Discovery with SNMP enabled listed all IP's in the range, even unused ones
• Auto-Upgrade of Windows SysOrb Agents didn't work when not on C:\
• Unknown status of some checks, although they actually were OK (green)
• A problem related to cluster recovery (for SysOrb ServerClusters)
• Performance too slow when rescanning the snmpChecks on a node
• Using 'percent' as the unit on Custom AgentChecks did not work
• The report generator could in some cases cause the SysOrb Server to restart
• A deletion of a report selection could return the error message 'unimplemented'

Download SysOrb 2.6 build 2638 here!

SysOrb 2.6 is now available!

January 30th, 2004: New features and improvements:

• Auto-Discovery - scan a given IP range and detect nodes
• NodeClasses - group your nodes across the hierarchy
• Option for moving nodes between SysOrb domains
• More flexible display and setting of real-time graphs
• More flexible setting of alerting options
• More precision in the setting of alert notification
• Links to AgentActions from the Overview section
• Info-box on which user you are currently logged in as
• Check Label - option for adding a text label to each check
• Links to resetting the ScoreKeeper score, and to Unexpected downtime from the Overview section

Download SysOrb 2.6 Here!!

Tip: Integrating to your Help Desk system..

December 16th, 2003: Did you know that you can use the SysOrb e-mail notification for integrating events into your existing Help Desk system?

Read more here!

New service update for SysOrb 2.4.4 available

December 15th, 2003: We have now released build 2481 of SysOrb 2.4.4 that contains a couple of bug fixes from the official SysOrb 2.4.4 release, as well as a number of performance-related improvements.

We recommend upgrading to this new build.

New version: SysOrb 2.4.4

November 24th, 2003: New features and improvements:

• Cumulative accounting checks - e.g. MB's transferred month-to-date etc.
• Custom Alert Path: Command line tool integration
• Comment field on individual checks, for easier identification
• Optional min/max values display on graphs
• Performance improvements
• New SysOrb Agent: Solaris 8/9 for IA32

Download SysOrb 2.4.4 now!

New version: SysOrb 2.4.3

September 26th, 2003: New features and improvements:

• HTTP-content NetCheck - get alerts if the content of your URL changes!
• CSV-file export - for exporting data to external tools
• Various web interface usability improvements
• Important database performance improvements

Download SysOrb 2.4.3 Now!

Tip: Using SysOrb as a 'sub-supplier'

September 5th, 2003: Did you know that you can use SysOrb as a supplier of monitoring for event notification to your existing management framework?

Read more here!

New version: SysOrb 2.4.2

August 27th, 2003:

New version: SysOrb 2.4.1

June 27th, 2003:

• PDA-optimized web interface
• Improved LogCheck feature - consolidate your log file scanning
• Java applet for integrating third-party tools
• Alert acknowledgement option
• Improved Alert messages
• New OS platforms: Solaris 2.6 and Windows 2003/XP

Download SysOrb 2.4.1 now!

SysOrb 2.4 is now available!

April 14th, 2003:

• Enhanced monitoring of Windows servers, through Performance Counters, Event Log, Custom Checks and more...
• New and improved SNMP monitoring
• AgentActions facilitate management
• Enhanced reporting capabilities
• Improved Web User Interface
• New OS platforms: SuSE and Mandrake Linux

Download SysOrb 2.4 now!

SysOrb 2.4 pre-release now available!

March 18th, 2003:

• Enhanced monitoring of Windows servers, through Performance Counters, Event Log, Custom Checks and more...
• New and improved SNMP monitoring
• AgentActions facilitate management
• Enhanced reporting capabilities
• Improved Web User Interface
• New OS platforms: SuSE and Mandrake Linux

Download the pre-release of SysOrb 2.4 here!

SysOrb 2.4 pre-release, known issues

March 11th, 2003:

Known issues in this pre-release:

• The official documentation has not yet been released
• Forecast graphs cannot be viewed
• Reports are very scarce on content, and sending HTML e-mail reports is currently not functional
• Historical data are not properly resynchronized in SysOrb ServerCluster configurations

Download the pre-release of SysOrb 2.4 here!

SysOrb 2.2.1 is now available!

July 5th, 2002: SysOrb 2.2.1 includes the following improvements over SysOrb 2.2:

• Agent for SuSE 7.3
• Agent for Novell NetWare 5.1
• Usability improvements like "copy" configuration from one node to a range of other nodes

Launch of SysOrb 2.2 at CeBIT 2002!

March 6th, 2002: The new SysOrb 2.2 will be launched at the CeBIT 2002 fair in Hannover, Germany. Read the press release for more information on added features.

New company name, design profile and web site!

November 6th, 2001: Our new company name, Evalesco Systems, reflects the dedication of the company. The word "evalesco" is latin and means: To grow strong, to prevail, to have value.

We are dedicated to:

• Delivering substantial value to our customers, assisting them in growing even stronger,
• Providing our employees with an environment that allows them to prevail and grow strong in their careers and their lives in general,
• Further increasing the strength and value of our products through a focused development effort, and
• Establishing strong, valuable partnerships with our customers and partners.

Through our dedication, we shall grow stronger!

To underline this dedication we have implemented a new corporate design profile and web site. If you have any comments on this or other issues, please contact us.

New release: SysOrb 2.0.1 is out!!

November 6th, 2001: Check out the latest version of the SysOrb Network Monitoring System with Test Drive or download the free 30-day Trial License!
SysOrb 2.0.1 includes new features like:

• Support for SMART IDE disk monitoring.
• Checks of DNS, POP-3, IMAP and FTP
• Support for HP-UX 11 via SysOrb Agent.
• Now also Solaris 8 support on the SysOrb Server.

SysOrb 2.0 is finally out.

May 7th, 2001: SysOrb 2.0 is available in the form of build 1184. Main changes since last:

• Linker and compiler induced problems in the RedHat 6.2 server build has been cured
• Solaris 8 on UltraSPARC is now supported (not with the SysOrb Server yet though)
• Various small communication-related bug-fixes in the clients on all architectures
• A very hard to trigger bug that could happen when running servers in a clustered configuration has been fixed
• A few more check types have been added (interface throughput and I/O queue length)

Also, we would like to draw your attention to our License Manager from where you can purchase and download SysOrb licenses to suit your needs.

SysOrb Milestone VIId is released

March 20th, 2001:This release includes the following fixes:

• Fixed the problems with the SysOrb Server refusing connections on
  Linux 2.4 kernels.
• Fixed problem where all the SysOrb Servers could sometimes die during a
  re-synchronization.
• Under very special circumstances the client would refuse to connect to the
  SysOrb Server. This is also fixed.
• The server and client logs have been cleaned up, so less diskspace
  should be required.

SysOrb Milestone VIIc have been released

March 15th, 2001: Changes in this release include:

A possible crash on Windows, especially when running with a lot of clients, have been fixed.

• A socket leak in the clients, when a server was down have been fixed.
• The FreeBSD packing should be very much improved. We've also moved from FreeBSD 3.4 to FreeBSD 3.5,and from FreeBSD-4.0 to FreeBSD-4.2.
• The client uses a lot less diskspace for it's logfiles.
• Other small bugfixes.

SysOrb Milestone VIIb is released

January 29th, 2001: SysOrb Milestone VIIb is released. This version fixes a bug in the Windows version of SysOrb which could cause the server to crash, when deleting a host. It also fixes a small logfile problems on Windows, where entries wasn't appended to the logfile, when the server was restarted.

Milestone VIIa released

January 17th, 2001: The new version of SysOrb is now uploaded to the server. It is Milestone VIIa with the build number 1002 (it still presents itself as Milestone VII).

Milestone VII has been released

January 15th, 2001: This version will hopefully become the final version in a few weeks.

• FreeBSD 4.0 port.
• Improved navigation in the web-interface
• Bugfixes

As this Milestone will probably become the final version, we are very much interested in hearing about bugs and misfeatures.

If you need to test SysOrb in a larger enviroment than the default license allows you, please contact us.

Debian packages available.

October 3rd, 2000: We finally got the Debian-packages building, and they are available from our download section.

Finally, the Milestone V release is ready!

August 14th, 2000: A number of stability and usability problems with the Milestone IV release has been addressed, besides that, the major news in this release are:

* New Web interface
* Client/server mutual authentication

Get missing shared library.

May 30th, 2000: Oops, someone forgot to upload the base shared library for the server / cgi packages for the Linux port :-) Sorry...

On the development side, we are moving towards the Milestone IV release, but there really is a lot of work in getting everything stabilized and in shape for a release. Feature-wise it is looking very promising though. Expect news here again in about a week.

SysOrb Milestone III postponed

April 19th, 2000: We postponed the Milestone III release because we wanted to fix a number of problems and include some specific features.

But now it is here, and you can get it from the download page. We encourage everyone to try out this release and tell us what you think.

There is now some preliminary documentation available as well, and an errata documenting the currently known problems. We will appreciate any feedback we can get on this release.

Work will start on the Milestone IV release as soon as the dust settles from the Milestone III release. The next milestone will feature, among other things,

* Mirroring support for multiple servers / distributed database
* Graphical User Interface, to supplement the Web Interface
* I2C support in the Linux client (for fan speed monitoring etc.)
* A number of fixes to problems mentioned in the errata.

SysOrb Milestone IIIb released

May 10th, 2000: A bugfix release to the MilestoneIII release is out now. It is build 419, or Milestone IIIb.

There is not much new in this release, except quite a few bugfixes and improved debugging capabilities to help us trace bug reports.

The Milestone IV release is progressing nicely, and we look forward to present you with 07.07, GSM 07.05 compliant serial devices.

The linux client can check software RAID devices in addition to fanspeed and temperatures using I2C with lm_sensors. (Requires patch for 2.2 kernels.) This release should be the last before the final release of SysOrb. We will now focus on bugfixing, and the final release should not contain any new features.

SysOrb Milestone II released

March 30th, 2000: Yet another bugfix and feature improvement to the MII release is out.

This time it is MIIc, aka. build 274. This release fixes a bug that could lead to crashes if hosts were removed from the monitoring system. Besides from that, the release includes numerous other bugfixes and the addition of various small features and enhancements.

Development is progressing well on MIII, which we plan to release on April 10th.

SysOrb Milestone II fixes release

March 17th, 2000: There is a bugfix release out for the MII release. This new release has build number 239, and the old plain MII release was Build 225.

This release fixes bugs mainly in the database backend and in the socket handling code for the clients.

We are now beginning work on MIII which will finally add SNMP support to the SysOrb product.

Finally SysOrb Milestone II is out.

March 13th, 2000: After a month of hard work, we are finally ready to present to you, the SysOrb Milestone II Release.

Some major changes have been made in the code, to pave the way for changes that are coming in the next Milestones. The two really big changes in this Milestone are:

• We now have our own database backend
• Most of the server infrastructure has been ported to NT

The new database backend allows searching the device and service histories, and is overall a lot faster than the old backend. Furthermore, it saves you the trouble of installing PostgreSQL if you do not have it on your system already.
We had hoped to have an NT version of the SysOrb Server ready for this release, but this port has been delayed. We hope to have a NT port out in a week or so.