Is there a way to disable the anonymous/guest mode, or at least prevent it from acting on nodes (disabling, etc)?

I missed the is_volatile option in statusengine.c, so i need to add: SERVICEOBJECT_INT(is_volatile); on service dumping

Statusengine 3 is available

Today I released the next generation of Statusengine, Version 3.

SE3 has a complete new code base, new database schema, and supports more database backends.
Read more about Statusenngine 3 at the project page: https://statusengine.org/

Why Statusengine 3?
Step by step Statusengine became more than a simple Event Broker Module. Three years ago, I started development of Statusengine to debug the Monitoring Core - seriously :D

Than I started to add feature, like database backend, performance data processor and so on. I never planned to do this, but i was annoyed...

To keep the code maintainable, it was time to refactor and to get rid of things...

Is Statusengine 2 dead now?
Due to the fact, that my spare time is limited I will not implement new features to Statusengine 2.

If you found a bug, or want to improve Statusengine, please don't hesitate to create an Issue or send an Pull Request!

Can I stay on Version 2?
Yes, why not! But keep in mind, that the Event Broker Module is this repository is getting older and older every day.
I would recommend you, that you use the event broker module from the new repository. It's 100% compatible! https://github.com/statusengine/module

Where is the documentation of Version 2?
Version 2 is now "old stable" and the documentation will be still available on the Statusengine project page.

New Repositories
To make it easier, I created a new GitHub organization for Statusengine, to split all components into a single repository.
All new developments are done there: https://github.com/statusengine

Feedback welcomed!

• You like Statusengine 3?
• You miss a feature or found a bug?
  Please don't hesitate to create an Issue!

MySQL increases the value of auto increment by every single ON DUPLICATE KEY UPDATEor REPLACE query.
Due to this, you can easily hit the auto increment max value.

So, i would recommend to truncate the prefix_hoststatus and prefix_servicestatus tables on every restart of the monitoring core, inside of the FINISH_OBJECT_DUMP event handler...

See: https://www.percona.com/blog/2011/11/29/avoiding-auto-increment-holes-on-innodb-with-insert-ignore/

This is an example of a system with 60 services.

Patch

--- cakephp/app/Console/Command/StatusengineLegacyShell.php
+++ cakephp/app/Console/Command/StatusengineLegacyShell.php
@@ -549,9 +549,15 @@ class StatusengineLegacyShell extends AppShell{
                                $this->activateObjects($this->dumpIds);

                                //Remove deprecated status records
-                               CakeLog::info('Delete deprecated status records');
-                               $this->removeDeprecatedHoststatusRecords($this->dumpIds);
-                               $this->removeDeprecatedServicestatusRecords($this->dumpIds);
+                               //Removed due to: https://www.percona.com/blog/2011/11/29/avoiding-auto-increment-holes-on-innodb-with-insert-ignore/
+                               //CakeLog::info('Delete deprecated status records');
+                               //$this->removeDeprecatedHoststatusRecords($this->dumpIds);
+                               //$this->removeDeprecatedServicestatusRecords($this->dumpIds);
+
+                               CakeLog::info('Truncate table hoststatus');
+                               $this->Hoststatus->truncate();
+                               CakeLog::info('Truncate table servicestatus');
+                               $this->Servicestatus->truncate();

                                $this->dumpIds = [];

When I try to integrate statusengine into naemon, I get the following error:

Could not load module '/opt/statusengine/statusengine.o' -> /opt/statusengine/statusengine.o: undefined symbol: hostescalation_ary

I use naemon on an Cent OS 7 with Naemon Core 1.0.5-pkg

On a nagios/naemon reload/restart the tables prefix_hoststatus and prefix_servicestatus should be cleaned up that deleted hosts and services will get removed out of the table

I've realized different things with the logging of statusengine cakephp application

1. The LegacyShell Daemon uses a hardcoded file handler to write the output to

2. The current hardcoded file handler logging doesn't log any timestamps in the logfile which makes it harder to analyse future possible problems or crashes.

3. The current code doesn't support logfile rotation. StatusengineLegacyShell.php could reopen (close/open) the logfile on SIGHUP or similar to support log rotation.

4. CakePHP provides a generic LogHandlerInterface which supports file, syslog and other handler. Is there a reason for not using the generic logging interface instead of fopen/fwrite? With generic logging and syslog you would tackle the logrotation problem also since logrotation can be taken care on the syslog server, etc

In the field Servicestatus.last_hard_state Statusenige writes 1970. I trached the error back to the function
servicestatusIdFromCache lines:
'last_hard_state_change' => date('Y-m-d H:i:s', $payload->servicestatus->last_hard_state_change),
'last_hard_state' => date('Y-m-d H:i:s', $payload->servicestatus->last_hard_state),

Rename the &client variable, because it gets "merged" with mod_gearmans client variable if both brokers are running in one naemon process!

Following the documented installation procedure leads to statusengine's PHP interface complaining about non-existence of MySQL table "users". Structure of that table can be found in the source code (https://github.com/nook24/statusengine/blob/master/sql/statusengine.sql), but that file is not mentioned anywhere in documentation.

A closely related issue is that this file create a default admin user, with a hardcoded password hash, yet the actual password seems not to be documented anywhere. It seems that either the default password should be documented and users be advised to immediately change that default password, or the documentation should explain how to create the initial user (which might be difficult given that MySQL doesn't support blowfish encryption).

Extend the parent singal handler by SIGINT

Since Statusengine 2.0.1 a restart of Statusengine is required after a new object was added, that should process perfdata.

Today I make available to my customers a modified version of https://exchange.nagios.org/directory/Addons/Frontends-%28GUIs-and-CLIs%29/Web-Interfaces/Simple-Nagios-PHP-Dashboard/, where I create the service groups in NagiosBPI (with a personalized field with the customer's name) and present a unique dashboard for each customer.

I would like to adopt StatusEngine, for my clients. My idea is, according to the @Domain of the login it loads only the hosts and services of that client.

Any suggestions on how I can implement this? It could even be an installation for each client (I create subdomains) and an environment variable for StatusENgine to search only the client's hosts and services information.

Any idea? # #

Gearman's server address is currently hard coded to 127.0.0.1 in the broker binary module. The address should be configurable through module arguments.

My use case is to have nagios-core (including the status engine module), run inside a dedicated docker container (with the web interface, gearmand and mysql each running in distinct containers). I am pretty sure that others persons might have other legitimate use case for this requirement.

In the core.php configuration the default logging stream is configured to be Syslog
https://github.com/nook24/statusengine/blob/master/cakephp/app/Config/core.php#L405-L409

but in the bootstrap.php two additional file logstreams are defined for error and debug. Is this by intention or some leftovers from the change to syslog issue #15?
https://github.com/nook24/statusengine/blob/master/cakephp/app/Config/bootstrap.php#L103-L112

When using the provided start script, several worker process are being started and forked into background without any real parent pid.

start-stop-daemon creates a pid file of the main php script which then gets closed after all worker processes are being created.

When calling the init script with the status parameter you get an error that statusengine is not running cause the pid file created by start-stop-daemon has already ended but the forked childs still live on.

When you try to stop statusengine it tells you that statusengine has already been stopped (the process to the pid file .... same as status).

If flaptedection is enabled, but no flap detection options are set, status engine will dump an not valide configuration to services table i guess.

Hi Nook,

We have a requirement that down time need to canceled when we cancelled for node.
currently we do not have that option.
could it possible to achieve that option with any UI code changes.
Could you please help on achieve this.

Thanks
Vijay

The query that CakePHP builds to truncate the tables is not that good because it is using IN($ALL_IDS)

DELETE `Command` FROM `naemon`.`naemon_commands` AS `Command`   WHERE `Command`.`command_id` IN (1188, 1189, 1190, 1191, 1192, 1193, 1194, 1195, 1196, 1197, 1198, 1199, 1200, 1201, 1202, 1203, 1204, 1205, 1206, 1207, 1208, 1209, 1210, 1211, 1212, 1213, 1214, 1215, 1216, 1217, 1218, 1219)

Solution: Replace with TRUNCATE TABLE ...