Merge pull request #629 from Icinga/release-1.1.1

Release 1.1.1

AUTHORS

@@ -1,5 +1,6 @@
 Alexander A. Klimov <alexander.klimov@icinga.com>
 Eric Lippmann <eric.lippmann@icinga.com>
+Feu Mourek <feu.mourek@icinga.com>
 Henrik Triem <henrik.triem@icinga.com>
 Johannes Meyer <johannes.meyer@icinga.com>
 Julian Brost <julian.brost@icinga.com>

CHANGELOG.md

@@ -1,5 +1,34 @@
 # Icinga DB Changelog
 
+## 1.1.1 (2023-08-09)
+
+This release fixes a few crashes in the Icinga DB daemon, addresses some shortcomings in the database schema,
+and makes the `icingadb-migrate` tool handle malformed events and other edge-cases more reliably.
+
+* Fix a possible crash when the Icinga 2 heartbeat is lost. #559
+* Retry additional non-fatal database errors. #593 #583
+* Make heartbeat compatible with Percona XtraDB Cluster. #609
+* Write a hint for empty arrays/dicts into `customvar_flat` for Icinga DB Web. #601
+* Warn about unknown options in the daemon config file. #605 #631
+* Don't log a port number for UNIX socket addresses. #542
+* Fix some custom JSON encode functions for `null` values. #612
+* Documentation: add TLS options to `icingadb-migrate` example config. #604
+* Documentation: Replace `apt-get` with `apt`. #545
+* Update dependencies. #548 #549 #588 #589 #590 #594 #595 #596 #598 #599 #603 #632
+
+### Schema
+
+* Allow longer names for notification objects. #584
+* Add missing indices to `hostgroup`, `servicegroup`, and `customvar_flat`. #616 #617
+* Change sort order of history event types. #626
+
+### icingadb-migrate
+
+* Ignore events that miss crucial information. #551
+* Fix a foreign key error for flapping history with `ido.from` set. #554
+* Fix a constraint violation for flexible downtimes that never started. #623
+* Show an error for unknown options in the config file. #605
+
 ## 1.1.0 (2022-11-10)
 
 This release adds a tool for migrating history from IDO. Apart from that,

doc/04-Upgrading.md

@@ -3,6 +3,22 @@
 Specific version upgrades are described below. Please note that version upgrades are incremental.
 If you are upgrading across multiple versions, make sure to follow the steps for each of them.
 
+## Upgrading to Icinga DB v1.1.1
+
+Please apply the `1.1.1.sql` upgrade script to your database.
+For package installations, you can find this file at `/usr/share/doc/icingadb/schema/mysql/upgrades/` or
+`/usr/share/doc/icingadb/schema/pgsql/upgrades/`, depending on your database type.
+
+Note that this upgrade will change the `history` table, which can take some time depending on the size of the table and
+the performance of the database. While the upgrade is running, that table will be locked and can't be accessed. This
+means that the existing history can't be viewed in Icinga Web and new history entries will be buffered in Redis.
+
+As the daemon checks the schema version, the recommended way to perform the upgrade is to stop the daemon, apply the
+schema upgrade and then start the new daemon version. If you want to minimize downtime as much as possible, it is safe
+to apply this schema upgrade while the Icinga DB v1.1.0 daemon is still running and then restart the daemon with the
+new version. Please keep in mind that depending on the distribution, your package manager may automatically attempt to
+restart the daemon when upgrading the package.
+
 ## Upgrading to Icinga DB v1.0
 
 **Requirements**

internal/version.go

@@ -7,4 +7,4 @@ import (
 // Version contains version and Git commit information.
 //
 // The placeholders are replaced on `git archive` using the `export-subst` attribute.
-var Version = version.Version("1.1.0", "$Format:%(describe)$", "$Format:%H$")
+var Version = version.Version("1.1.1", "$Format:%(describe)$", "$Format:%H$")