Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upcoming Changes: Drop support for Nagios Core #34

Open
nook24 opened this issue Sep 5, 2023 · 3 comments
Open

Upcoming Changes: Drop support for Nagios Core #34

nook24 opened this issue Sep 5, 2023 · 3 comments

Comments

@nook24
Copy link
Member

nook24 commented Sep 5, 2023

In the near future, you can expect some breaking changes happen to the Statusengine Broker. While there is no fixed ETA yet, we will drop the support for Nagios Core. In the past we were trying to keep Statusengine as compatible as possible. However, both projects are slightly drifting apart which makes it harder and harder to keep compatible with both.
In addition, we will drop support to be backwards compatible with older versions of Naemon. This means that Statusengine will maybe work with older releases of Naemon, but maybe also not. In case you fetch any issues, simply update your Naemon version.

Why?

  • At the moment, the backwards compatibility is holing new features back, like implementing Support for expiring acknowledgements (Available since Naemon 1.4.0)
  • My time is limited
  • My C skills are limited as well :)
  • There is a pending pull request Switch build system and update toml11 #32 to get rid of meson build system

How does this affect me, the user?

  • If you are using Nagios Core, you should consider to migrate your setup to Naemon. The migration should be straightforward as Naemon is a 1:1 drop-in replacement.
  • If you are using Naemon Core you are probably not affected by this, except you are using an old Naemon version.
  • You could also considering to use a monitoring suite like https://openitcockpit.io/ (open source) which will take care of updating Naemon, Statusengine and all other tools required by itself.

Can I still use the old Broker version with Nagios Core?
Yes. While I can not recommend doing this, because you will not receive any future updates and patches.

I'm a developer and want to help to keep Nagios Core support alive
Contributors are welcomed! Just respond to this issue or drop me a mail.

@nook24 nook24 pinned this issue Sep 5, 2023
@eanselmi
Copy link

I love the initiative of keeping Nagios Core support alive!

@sistemmsn
Copy link

It still works great, I just compiled the broker and worker, I am using the worker from a container since it uses php7.4.

Currently, I am running it on nagios 4.4.14

@nook24
Copy link
Member Author

nook24 commented Sep 27, 2023

I love the initiative of keeping Nagios Core support alive!

@eanselmi are you interested in providing development and maintenance to ensure that the broker continues to support Nagios?

It still works great, I just compiled the broker and worker, I am using the worker from a container since it uses php7.4.

@sistemmsn The Statusengine Worker is not is not affected by this change. PS: It's also works fine with php 8.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants