Skip to content

Commit 30149c5

Browse files
committed
Docs: Add 2.13 upgrading documentation
1 parent 2796302 commit 30149c5

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed

doc/16-upgrading-icinga-2.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,39 @@ Specific version upgrades are described below. Please note that version
88
updates are incremental. An upgrade from v2.6 to v2.8 requires to
99
follow the instructions for v2.7 too.
1010

11+
## Upgrading to v2.13 <a id="upgrading-to-2-13"></a>
12+
13+
### DB IDO Schema Update <a id="upgrading-to-2-13-db-ido"></a>
14+
15+
There is an optional schema update on MySQL which increases the max length of object names from 128 to 255 characters.
16+
17+
Please proceed here for the [MySQL upgrading docs](16-upgrading-icinga-2.md#upgrading-mysql-db).
18+
19+
### Behavior changes <a id="upgrading-to-2-13-behavior-changes"></a>
20+
21+
#### Deletion of child downtimes on services
22+
23+
Service downtimes created while using the `all_services` flag on the [schedule-downtime](12-icinga2-api.md#schedule-downtime) API action
24+
will now automatically be deleted when deleting the hosts downtime.
25+
26+
#### Windows Event Log
27+
28+
Icinga 2.13 now supports logging to the Windows Event Log. Icinga will now also log messages from the early
29+
startup phase to the Windows Event Log. These were previously missing from the log file and you could only
30+
see them by manually starting Icinga in the foreground.
31+
32+
This feature is now enabled and replaces the existing mainlog feature logging to a file. When upgrading, the installer
33+
will enable the windowseventlog feature and disable the mainlog feature. Logging to a file is still possible.
34+
If you don't want this configuration migration on upgrade, you can opt-out by installing
35+
the `%ProgramData%\icinga2\etc\icinga2\features-available\windowseventlog.conf` file before upgrading to Icinga 2.13.
36+
37+
#### Broken API package name validation
38+
39+
This version has replaced a broken regex in the API package validation code which results in package names
40+
now being validated correctly. Package names should now only consist of alphanumeric characters, dashes and underscores.
41+
42+
This change only applies to newly created packages to support already existing ones.
43+
1144
## Upgrading to v2.12 <a id="upgrading-to-2-12"></a>
1245

1346
* CLI

0 commit comments

Comments
 (0)