KuvaszUptime

Docker hub: kuvaszmonitoring/kuvasz:3.9.0

docker pull kuvaszmonitoring/kuvasz:3.9.0

Documentation: v3.9.0 - kuvasz-uptime.dev

Features

• Added a new property called monitorDetailsUrl to the webhook messages (also available in the webhook templates as ctx.monitorDetailsUrl), which is a relative URL to the affected monitor's details page on the UI. This allows you to easily include a direct link to the monitor's details page in your webhook notifications, so you or your team can quickly access more information about the incident and take necessary actions.
• The webhook request headers can be templated from now on, so you can include dynamic values in the headers as well, based on the context of the event that triggered the webhook.

Fixes

• Fixed a bug in the webhook templating logic that caused templates fail to render in case the ctx.monitorUrn variable was referenced inside.

Docs

• Added a dedicated section of webhook examples for 3rd party services (with ntfy included).

Full Changelog: https://github.com/kuvasz-uptime/kuvasz/compare/3.8.0...3.9.0

Docker hub: kuvaszmonitoring/kuvasz:3.8.0

docker pull kuvaszmonitoring/kuvasz:3.8.0

Documentation: v3.8.0 - kuvasz-uptime.dev

By adding the webhooks support, this release introduces a huge step towards making Kuvasz more extensible and integrable with other systems. Webhooks allow you to send real-time notifications about monitor status changes to any 3rd party service, or even to your own custom-built solutions, without the need for a built-in integration.

Features

• Webhooks are in da house! 🎉 With the (optional) custom template support, and the ability to include your own headers, the number of use-cases you can cover with webhooks is pretty much endless. You can set them up just like any other integration, for further details, please refer to the documentation.
• It's now possible to exclude certain events from an integration's triggering conditions, by using the new excluded-events attribute of the integration configuration.
• Added a new endpoint to the API under GET /api/v2/status-pages/{statusPageId}/details where you can get the same details of a status page as on the UI, including the monitors' incident stats, so you can build your own custom status pages or integrate the details into your existing system. In case you want to get the details of a public status page, you don't even have to be authenticated, in order to be able to build publicly available status pages on your own. For further details, please refer to the API documentation.

Full Changelog: https://github.com/kuvasz-uptime/kuvasz/compare/3.7.1...3.8.0

Docker hub: kuvaszmonitoring/kuvasz:3.7.1

docker pull kuvaszmonitoring/kuvasz:3.7.1

Documentation: v3.7.1 - kuvasz-uptime.dev

Fixes

• Reverted the base image change from 3.7.0, because it caused incompatibility issues with older CPUs that don't support x86-64-v3

Full Changelog: https://github.com/kuvasz-uptime/kuvasz/compare/3.7.0...3.7.1