kuvasz-uptime/kuvasz 4.7.0

v4.7.0

on GitHub

Documentation: v4.7.0- kuvasz-uptime.dev

docker pull kuvaszmonitoring/kuvasz:4.7.0

Features

• More than one recipient for an email integration: the to-address of an email integration can have several addresses now, either as a list in your YAML file, or as one value with the addresses separated by commas (handy for environment variables). By default, every recipient gets an email of their own, so they don't see each other's addresses, and one wrong address doesn't stop the others from getting the email. If you'd rather like to send one email with every recipient in its "To" field, disable the new separate-emails option. Your existing email integrations keep working without any change. In the API response of the integrations, the new toAddresses field lists the recipients, and separateEmails shows how they get the emails. The toAddress field is deprecated: it still works, and it contains every recipient, separated by commas.

Fixes

• Sending emails without encryption was not possible: the documentation said that the SMTP transport strategy sends emails without encryption, but it actually switches to an encrypted connection (STARTTLS) whenever the mail server offers it. So, if your mail server offered encryption with a self-signed certificate, or with one from your own certificate authority, Kuvasz did not trust it, and failed to start. If you want to send emails without encryption, even if the server offers it (e.g. on a local network), use the new SMTP_PLAIN transport strategy. The SMTP one works as before, and its documentation is fixed too (#577).

Full changelog: 4.6.0...4.7.0