search

Icinga / icinga2

The core of our monitoring platform with a powerful configuration language and REST API.
https://icinga.com/docs/icinga2/latest
GNU General Public License v2.0
2.03k stars 579 forks source link

Deprecate Windows C Plugins, replaced by Icinga for Windows #8141

Closed bobapple closed 8 months ago

bobapple commented 4 years ago

Plugins for Windows monitoring, included in Icinga 2, should be deprecated. The replacement, Icinga for Windows, is the new standard selection for monitoring Windows servers with Icinga and we should not offer two separate solutions.

The Icinga 2 documentation will be updated to match this accordingly, as described in https://github.com/Icinga/icinga2/issues/8069

Al2Klimov commented 4 years ago

Was #8071 not the only task for this?

bobapple commented 4 years ago

Yes, that should be all for now.

The documentation changes described in #8069 need some more attention and some additional steps which we may plan for a future release.

Crunsher commented 4 years ago

Finally someone takes care of my crimes

dnsmichi commented 4 years ago

Finally someone takes care of my crimes

Powerful and easy to kickstart your monitoring setup on Windows for anyone knowing the behaviour from Linux/Unix, working OOTB after the msi install. I'm still glad we moved there in 2015 and made it as convenient as possible.

No regrets my friend, your contributions will always be remembered 👍 Too bad we couldn't find a better trainee project loosely coupled to the core's code back then. Just think of large enterprises and cooperations running it in production for 5 years, no matter the bugs or crimes we did. 😎

kochd commented 4 years ago

Just think of large enterprises and cooperations running it in production for 5 years, no matter the bugs or crimes we did.

This leads me to my question: Are we supposed to migrate the endpoints and service configurations now as soon as possible? Or does deprecated mean it will be provided as it is as long as possible in case there is no major bug or security issue found. Just like many others I've build tons of things based on that now deprecated system including the easy to integrate custom checks in sbin. The blog post did not make this clear to me either.

As I have a large set of well established service checks I integrate new endpoints based on them instead of using the powershell plugins at all . Using the powershell plugins would mean I have to implement everything again from scratch just to get what I had before.

Can somebody clarify?

Al2Klimov commented 4 years ago

IMAO still shipping the plugins for a while doesn't hurt (us) – especially while a lot of people are still using them.

mcktr commented 4 years ago

The deprecated C/C++ Windows plugins should be shipped at least for the next major version. It may is also a good idea to make this more visible with a warning message when validating the configuration.

gunnarbeutner commented 4 years ago

Finally someone takes care of my crimes

Eh, they sure served their purpose. Plus whatever else Michael already wrote. 🙏

Al2Klimov commented 4 years ago

All (!) of the three very first Icinga 2 core devs join the discussion? Just this fact shows... a lot.

Even w/o this I have no problem with shipping those now unmaintained stuff (#8071, #8051, compat) even forever – as long as we won't have to even think about it while developing everything else.

kochd commented 4 years ago

Even w/o this I have no problem with shipping those now unmaintained stuff (#8071, #8051, compat) even forever

Sounds good to me

Al2Klimov commented 1 year ago

@bobapple Does #9767 satisfy your needs?

bobapple commented 1 year ago

👍

Al2Klimov commented 1 year ago

Does that mean that this issue is resolved?