Question

Acknowledge an alert without forcing a check from the resources status page

  • 28 April 2023
  • 1 reply
  • 105 views

Badge +1

Hello,

I am using Centreon DSM and I have noticed that when I acknowledge a slot, the slot executes it’s check command and pass into OK status, so I checked centengine.log file and I have found that two command were executed (acknowledge and force_check ), so am asking if there is a way to disable the force check when acknowledge an alert from the resources status page.

We have the possibility to enable/disable a force_check in the old interface, but not in the new interface.

 

Acknowledge: Resources status (no option to disable force_check)

 

Acknowledge: Status Details → Services (with option to disable/enable force_check)

 

centengine.log file

[1682693066] [1000] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;linux-1;SnmpGatewayTraps_0002;2;0;1;admin;Acknowledged by admin


[1682693066] [1000] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;linux-1;SnmpGatewayTraps_0002;1682693064

 

 

Centreon 21.10

 

Thanks.

Best regards.


1 reply

Badge +2

Hi Marouane,

Indeed, this is a feature that has been implemented by Centreon in version 23.04 (unfortunately for you, who is on 21.10).

Take a look at the announcement made by Centreon: https://www.centreon.com/centreon-23-04-discover-the-latest-release/

Here's an quote:

Check vs Check Forced: You Need Both

Resource Status is the real-time view to track warning and critical events and act upon them. As a productivity tool, this user interface comes with many shortcuts to help quickly diagnose and troubleshoot incidents. One capability is to immediately check the current value of a monitored metric, typically to ensure the problem has been solved, hence the big Check button at the top of the page (as well as an icon on each resource).

You can now specify the type of check command, either a simple Check (that takes check periods into account) or Check Forced (performs checks ignoring check periods).

 

However, you have the possibility to completely disable this additional action via the ACL actions configuration (Administration > ACL > Actions Access) with the following parameters. But I don't think this is exactly what you are looking for.

Perhaps it would be possible to comment out the PHP code responsible for this action by searching for the corresponding portion of code in the web application (to be confirmed). However, please note that this could potentially break the application and any modifications would be erased during subsequent updates.

Reply