Bischeck
-
Release Notes

Version 1.1.2
2014-11-23


Legal Notice Copyright
© 2013-2014 Ingenjörsbyn AB.
This document is licensed by Ingenjörsbyn AB under the Creative Commons Attribution-ShareAlike 3.0 Unported License, http://creativecommons.org/licenses/by-sa/3.0/. If you distribute this document, or a modified version of it, you have to provide attribution to Ingenjörsbyn AB. and provide a link to the original.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
Nagios® is an official trademark of Nagios Enterprise Inc.
All other trademarks are the property of their respective owners.


Abstract

Abstract
This document describe the release history of Bischeck. For more information about specific bugs and feature requests please visit http://gforge.ingby.com/gf/project/bischeck/tracker
Table of Contents

1 Release 1.1.2 - 2015-11-23

Release 1.1.2 is a bug fix release.

1.1 New features

1.2 Bugs fixed and important issues

1.3 Upgrading

Release 1.1.2 support upgrade from release 1.1.X.

2 Release 1.1.1 - 2014-09-23

Release 1.1.1 is a minor upgrade of Bischeck. The most important is a fix for a major performance issue related to time based queries. Even if the performance issue was reported as bug, the result was correct. If you store a high number of items per service definitions in the cache, +1000, you should definitely upgrade.

2.1 New features

2.2 Bugs fixed and important issues

2.3 Upgrading

Release 1.1.1 support upgrade from release 1.1.0.

3 Release 1.1.0 - 2014-06-16

Release 1.1.0 is a minor upgrade of Bischeck with some new features.

3.1 New features

3.2 Bugs fixed and important issues

3.3 Upgrading

Release 1.1.0 support upgrade from release 1.0.0, 1.0.1 and 1.0.2. If you upgrade from 0.4.3 please upgrade to version 1.0.x first.

4 Release 1.0.2 - 2014-04-04

Release 1.0.2 is a minor bug fix release.

4.1 New features

None

4.2 Bugs fixed and important issues

4.3 Upgrading

Release 1.0.2 support upgrade from release 0.4.3, 1.0.0 and 1.0.1. If you upgrade from 0.4.3, please follow the upgrade instructions described in the below upgrading section for 1.0.0.

5 Release 1.0.1 - 2014-03-27

Release 1.0.1 is a minor bug fix release, but fixing a major bug related to threshold management.

5.1 New features

None

5.2 Bugs fixed and important issues

5.3 Upgrading

Release 1.0.1 support upgrade from release 0.4.3 and 1.0.0. If you upgrade from 0.4.3, please follow the upgrade instructions described in the below upgrading section for 1.0.0.

6 Release 1.0.0 - 2014-03-15

Release 1.0.0 is a major upgrade of Bischeck.

6.1 New features

6.2 Bugs fixed and important issues

6.3 Upgrading

Release 1.0.0 support upgrade from release 0.4.3. The install scripts upgrade option will not migrate the 0.4.3 cache to Redis automatically. After the upgrade has been ran the following steps must be conducted to migrate the cached Bischeck data to Redis.
  1. First run the migration according to the procedure in the “Bischeck installation and administration guide”.
  2. Make sure Bischeck is not started, but that Redis is started when doing the following steps.
  3. Make sure the Redis related properties in the properties.xml of the new installation is correct according to your Redis installation. The data migration program MoveCache2Redis will use the setting in the properties.xml or if not set use the default values. Please see the “Bischeck installation and administration guide” for more information.
  4. Run the data migration program supplied with Bischeck in the following way:
    $BISHOME/bin/bischeck migration.MoveCache2Redis
    
    or if the cache file is located in different location then default:
    $BISHOME/bin/bischeck migration.MoveCache2Redis -f /tmp/lastStatusCacheDump
    
    $BISHOME should be replaced with the path to the location of the newly installed Bischeck installation directory. The data migration program can be run with the -v option to show the data migration in verbose mode. You can also run the data migration just in test mode by using the flag -c. If the migration of cache data fails it can be rerun, but the Redis data storage should be flushed using the Redis FLUSHDB command. For more information about Redis please visit http://redis.io/.

7 Release 0.4.3 - 2013-03-27

This release is a minor upgrade.

7.1 New features

7.2 Bugs fixed and important issues

7.3 Upgrading

Release 0.4.3 support upgrade from release 0.4.2.

8 Release 0.4.2 - 2012-12-21

Except for the new features introduced and bugs that has been fixed in 0.4.2, there has also been some major work in making Bischeck more stable and performance enhancements running many host, service and service items configurations. Our goal has been to secure a stable resource utilization of the Java virtual machine (jvm) when running Bischeck over a long period of time.

8.1 New features

8.2 Bugs fixed and important issues

8.3 Upgrading

Release 0.3.3, 0.4.0 and 0.4.1 is supported for upgrade to 0.4.2. The upgrading is NOT applicable for release candidate.

9 Release 0.4.1 - 2012-10-01

9.1 New features

9.2 Bugs fixed and important issues

9.3 Upgrading

Release 0.4.0 is supported for upgrade to 0.4.1.

10 Release 0.4.0 - 2012-08-31

10.1 New features

10.2 Bugs fixed and important issues

10.3 Upgrading

Release 0.3.3 and 0.4.0_RC2 are supported for upgrade to 0.4.0.

11 Release 0.3.3 - 2011-11-14

11.1 New features

11.2 Bugs fixed and important issues

12 Release 0.3.2 - 2011-07-29

12.1 New features

12.2 Bugs fixed and important issues

13 Release 0.3.1 - 2011-04-08

13.1 New features

13.2 Bugs fixed and important issues

13.3 Upgrade issues

14 Release 0.3.0 - 2011-03-03

14.1 New features

14.2 Bugs fixed and important issues