Statusengine 3 - FAQ

[nook24]

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!