Releases: incident-io/icinga2-plugin
Releases · incident-io/icinga2-plugin
Release list
v0.2.0
Added
IncidentIoIcingaWebStyleselects the Icinga Web 2 front end thatsource_url
points at:icingadbfor Icinga DB Web, ormonitoringfor the older
monitoring module. Previously only Icinga DB Web was addressable, so the link
on every alert was a 404 for estates that have not migrated. Defaults to
icingadb, and is read throughglobalsso that leaving it unset is not a
configuration error.SECURITY.mdandCONTRIBUTING.md.
Changed
- The Icinga Director basket now carries only the two custom variable fields,
incident_ioandincident_io_metadata. It previously shipped its own
Command,UserandNotificationTemplate, duplicating objects the package
already installs toconf.dwith versions that could not work: the command
had noenvblock, so nothing reached the handler, and no notification was
ever applied to a host or service. Director cannot setenvon a command at
all, so those objects were never going to be Director's to own. Setting
vars.incident_ioon Director-managed objects is the one thing Director is
needed for, and that is what the fields do. The orphanedDataListis gone
too; the boolean field never referenced it.
Fixed
make basketfailed on a clean checkout, redirecting into adist/directory
that is gitignored and never created.docs/TROUBLESHOOTING.mdtold operators to run the handler asnagios.
Icinga 2 runs asicingaon both Debian and RHEL families.- The example payload in the README omitted
servicegroups, which service
alerts do carry. - Repository URLs still pointed at
incident-io/icinga2, including the
Homepagefield baked into every package. - CI now checks that the version the handler reports matches the
VERSION
file. Only the file was checked against the tag, so a release could ship
packages built as 0.2.0 whose--versionand User-Agent still said 0.1.0.
edge (tip of main)
Rolling build of the tip of main, replaced on every merge. Not a
stable release.
Packages here are versioned 0.2.0~git20260826.f9d418e, which sorts before
0.2.0 for both dpkg and rpm, so installing from edge still
upgrades cleanly once that version is tagged.
Built from f9d418e.
v0.1.0
Initial release.
Added
incident-io-icinganotification handler: POSIX sh, no jq, Perl or Python.- Host and service notification apply rules, opt-in per object via
vars.incident_io. - Arbitrary metadata passthrough via
vars.incident_io_metadataand
vars.incident_io_metadata_vars, encoded with Icinga's ownJson.encode(),
so nested dictionaries, arrays, numbers and booleans all survive intact. - Estate-wide metadata defaults via
globals.IncidentIoDefaultMetadata. source_urlon each alert, linking back to the object in Icinga Web 2.- Deduplication keyed on host and service name, so a RECOVERY resolves the alert
its PROBLEM opened and the key is identical across HA masters. - Notification type mapping, including resolving on
DOWNTIMESTARTso planned
maintenance does not hold an alert open. - Test suite covering escaping, metadata splicing, status mapping and
portability acrosssh,dash,bashandksh. .deband.rpmpackaging via fpm.- Icinga Director basket generator, under
contrib/. - Release automation: pushing a
v*tag publishes the built packages to GitHub
Releases with notes from this file, and every merge tomainrefreshes a
rollingedgeprerelease whose packages are stampedVERSION~git<date>.<sha>
so they sort before the tagged version and upgrade cleanly to it.