Create top-level views of your applications in a graphical editor. Rules express dependencies between existing hosts and services and let you alert on application level. Business processes are displayed in a tree or list overview.
You can find all issues related to this release on our roadmap.
Included changes can be found on the milestone: https://github.com/Icinga/icingaweb2-module-businessprocess/milestone/9?closed=1 And a detailed description about the most important ones on our blog: https://icinga.com/blog/2023/10/17/releasing-icinga-business-process-modeling-v2-5/
The main intention of this release is to add support for Icinga DB Web v1.0 and v1.1 in parallel.
Though, some additional bug fixes from the upcoming v2.5.0 release are also included:
You can find all issues related to this release on our roadmap.
This minor release fixes an issue with CSS not loading if using this module together with Icinga Web 2 v2.9.
You can find all issues and feature requests related to this release on our roadmap.
icingacli businessprocess process check
The check command used to just ignore acknowledgements and downtimes. So we added two new switches that make it possible to set the state to OK, if the node is acknowledged or in downtime.
--ack-is-ok
and --downtime-is-ok
for setting the respective state to OK.--blame
is for only showing nodes that have the same state as the process itself.--root-cause
shows only the path that causes a problem.display_name
Before this version the object name property was used for the host and service nodes. Since this is the unique identifier for the object, this can lead to it being pretty unreadable.
From now on we use the display_name
property for better readability, like in Icinga Web.
display_name
to fit with Icinga Web #102monitoring/filter/objects
restriction now get a properly filtered list of hosts and services
while adding new nodes.
#67
businessprocess/showall
were previously not able
to see configurations if they were also restricted by other roles.
#200
Unbound nodes
(nodes not being shown at top level and not in use as a sub
node) are now reachable through a fake nodeUNKNOWN
(or UNREACHABLE
when
being a host node). The former behavior comes from Icinga 1.x, as a reload
there had the potential to trigger false alarms. This is no longer an issue
with Icinga 2.x, allowing us to be strict once again when it goes to missing
nodesFirst stable release