Changelog for centreon-engine-19.10.18-2.42.i586.rpm :

* Wed Apr 28 2021 ecsos - Update to 19.10.18 - HOSTGROUPNAME and SERVICEGROUPNAME macros could lead to segfault if used on service/host without group.
* Wed Apr 28 2021 ecsos - Update to 19.10.17 - Mon 6538 Engine doesn\'t respect user\'s defined notification periods - fix(notification) the timeperiod are now filtered for the contact- Changes from 19.10.16 - chore(doc): release updated to 19.10.16
* Thu Sep 17 2020 ecsos - Update to 19.10.15 - fix(macros) : HOST & SERVICE problem id - fix(macros): last and current problem id was equal
* Tue May 12 2020 ecsos - Update to 19.10.14 - fix(macros): In several cases, macros were not replaced
* Tue Mar 24 2020 ecsosAATTopensuse.org- Update to 19.10.13
* Bug fixes - Centreon connectors timeout The timeout applied on checks execute by connectors were shorter than the timeout passed as parameter (near of 1s of difference). To fix this, timeouts are checked as milliseconds values now (more accurate) and the good duration is considered by connectors. - Volatile services and notifications This version of Engine fixes the following behabiour: if a service is volatile, configured to send normal notifications. It won\'t send anymore them if it is in downtime.
* Fri Mar 20 2020 ecsosAATTopensuse.org- Insert configuration for dbus.
* Wed Mar 11 2020 ecsosAATTopensuse.org- Update to 19.10.12
* Bug fixes - Service checks Multiline service check outputs were badly parsed and this lead to corruptions of status.dat/retention.dat files. - Downtimes removal One downtime could be removed during the removal of an other downtime. - XXX_SERVICEGROUP_XXX external commands XXX_SERVICEGROUP_XXX external commands were buggy. They take one servicegroup name as argument, it was resolved as a service name and not as a service group name.- Run spec-cleaner.
* Mon Feb 10 2020 ecsosAATTopensuse.org- Update to 19.10.11
* Bug fixes - Downtime cancellation was buggy The downtime cancellation is fixed now. - TOTALHOST
* TOTALSERVICES macros Some global macros like TOTALHOST
* and TOTALSERVICES were replaced by empty strings instead of numeric values.
* Wed Feb 05 2020 ecsosAATTopensuse.org- Update to 19.10.10
* Bug fixes - stalk options on services Stalk options were changed on modified services when engine was reload or restarted.
* Mon Jan 27 2020 ecsosAATTopensuse.org- Update to 19.10.9 - fix(customvariable): modified is set to false in the constructor (#334)
* Tue Jan 07 2020 ecsosAATTopensuse.org- Update to 19.10.8
* Bug fixes - fix(dt): some overflow can occurs (#319)
* Wed Nov 27 2019 ecsosAATTopensuse.org- Update to 19.10.7
* Bug fixes - Groups update with deleted object On object deletion, the groups containing these objects were not updated. So on group update (conf reload, not restart) the group keeps in its members a deleted object and can use it.
* Wed Nov 20 2019 ecsosAATTopensuse.org- Update to 19.10.6
* Bug fixes - Escalations When a host or a service linked to an escalation was deleted, there was an attempt to remove the host or the service twice. This behaviour led to a cancellation of the new configuration during a reload.
* Wed Nov 06 2019 ecsosAATTopensuse.org- Update to 19.10.5
* Bug fixes - Notifications retention In case of engine restart, notifications already sent were lost. It may have impacts on normal notifications when it is time to send a recovery notification. After a restart, the recovery notification was never sent.
* Mon Nov 04 2019 ecsosAATTopensuse.org- Update to 19.10.4
* Bug fixes - Custom variable update crash on reload A bug was introduce in 19.10.2 with a reload on custom_variables services/contacts/hosts update. - Recovery notification didn’t work on escalation [1;0] If an escalation was defined with a first notification at 1 and a last notification at 0, we want the escalation to start from the first notification, but only one time, the recovery notification was not sent.
* Thu Oct 31 2019 ecsosAATTopensuse.org- Update to 19.10.3
* Bug fixes - Service escalation not well resolved Service configurations look up failed when service escalations were defined.
* Tue Oct 29 2019 ecsosAATTopensuse.org- Update to 19.10.2
* Bug fixes - Custom variables not resolved Some custom variables were not resolved. This results in bad or pending checks with wrong commands. - Random host statuses Some hosts/services were changing status randomly. - Send custom variables to broker Some broker notifications about customvariables were dropped. - Null string crash In some cases strings construction could lead to exceptions thrown.
* Wed Oct 23 2019 ecsosAATTopensuse.org- Update to 19.10.1
* Bug fixes - This version fixes a crash that can occur when executing external commands.- Changes from 19.10.0
* Bug fixes - Notifications The notifications mechanism has been totally rewritten. First notification delay and last recovery notification delay should work as expected. - Pipes in results Pipes are allowed in the centreon-engine plugin return value.
* Improvements - Optimizations Migration of the code to C++11. This implies many changes in data structures. Some parts have also been rewritten and optimized. - Cmake cleanup The build directory is gone away. CMake is used as intended, this solves issues with some ide (like kdevelop)... - Better test coverage We now have 123 new unit test (+63%). It allow us to have a better code coverage of the code base.
* Fri May 17 2019 ecsosAATTopensuse.org- Update to 19.04.1
* Bug fixes - Hosts and contacts custom macros are not inserted into centreon_storage db. The custom macros added to the hosts and contacts objects are not inserted into centreon_storage database. That’s why it is not possible to filter by criticity in “Monitoring > Status Details > Hosts” page.- changes from 19.04.0
* Bug fixes - Hosts and contacts custom macros are not inserted into centreon_storage db. The custom macros added to the hosts and contacts objects are not inserted into centreon_storage database. That’s why it is not possible to filter by criticity in “Monitoring > Status Details > Hosts” page.- Drop centreon-engine-destdir.patch because now in upstream.
* Mon Oct 29 2018 ecsosAATTopensuse.org- update to 18.10.0 - no changelog from upstream- Remove changes for std::unique_ptr
* Tue Jul 24 2018 ecsosAATTopensuse.org- change std::auto_ptr to std::unique_ptr