RFC: incubator is to be discontinued
Hi, We had a discussion with our Debian maintainer about the fate of syslog-ng-incubator. For those of you who don't know, it is a set of syslog-ng modules not integrated to syslog-ng master for one reason or another. It is available from here: https://github.com/balabit/syslog-ng-incubator The problem with this repository is that it is not really maintained, causing compilation and functionality issues down the line. So our opinion is to go ahead and integrate stuff that can be brough up to speed. Once we've done what we could, we would discontinue the incubator altogether. Please speak up now, if you disagree, but please also be ready to help us out in maintenance in that case. If there are no disagreements in the following week, we would start to phasing out the incubator. We welcome volunteers to: 1) migrate code, OR 2) help with testing If you are the user of any of those plugins, letting us know at this point also helps making sure that no functionality is lost. Thanks. -- Bazsi
Hi, As far as I can see, the kafka-c module is definitely in active use. I added Pyr -- the original author of the kafka module -- on CC. In addition I see once in a while that people are asking about grok and zmq. On the other hand I'm not sure how much functional these modules are (AFAIR the the source part of the ZMQ module was never really finished) and the grok module builds on a C library which is not actively maintained for many years. I don't recall people mentioning any of the other modules recently. Bye, Peter Czanik (CzP) <peter.czanik@balabit.com> Balabit / syslog-ng upstream https://www.balabit.com/blog/author/peterczanik/ https://twitter.com/PCzanik On Sun, Jul 30, 2017 at 7:40 PM, Scheidler, Balázs < balazs.scheidler@balabit.com> wrote:
Hi,
We had a discussion with our Debian maintainer about the fate of syslog-ng-incubator. For those of you who don't know, it is a set of syslog-ng modules not integrated to syslog-ng master for one reason or another.
It is available from here:
https://github.com/balabit/syslog-ng-incubator
The problem with this repository is that it is not really maintained, causing compilation and functionality issues down the line.
So our opinion is to go ahead and integrate stuff that can be brough up to speed. Once we've done what we could, we would discontinue the incubator altogether.
Please speak up now, if you disagree, but please also be ready to help us out in maintenance in that case.
If there are no disagreements in the following week, we would start to phasing out the incubator.
We welcome volunteers to:
1) migrate code, OR 2) help with testing
If you are the user of any of those plugins, letting us know at this point also helps making sure that no functionality is lost.
Thanks.
-- Bazsi
____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/? product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
There is a popularity chart for debian packages: https://qa.debian.org/popcon.php?package=syslog-ng-incubator Of course it only shows how many computers it is installed to and does not means that the module is also in actively used. But because these modules should be installed by hand, a significant correlation should be there. So, it shows, that the most popular package amongst the debian users is the perl package. The kafka module and the syslog-ng-mod-basicfuncs-plus package is in the second most installed part of the incubator. The grok package and the zmq package has not installed (reported to be installed) at all. From: syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Czanik, Péter Sent: Wednesday, August 02, 2017 9:43 PM To: Syslog-ng users' and developers' mailing list; Pierre-Yves Ritschard Subject: Re: [syslog-ng] RFC: incubator is to be discontinued Hi, As far as I can see, the kafka-c module is definitely in active use. I added Pyr -- the original author of the kafka module -- on CC. In addition I see once in a while that people are asking about grok and zmq. On the other hand I'm not sure how much functional these modules are (AFAIR the the source part of the ZMQ module was never really finished) and the grok module builds on a C library which is not actively maintained for many years. I don't recall people mentioning any of the other modules recently. Bye, Peter Czanik (CzP) <peter.czanik@balabit.com<mailto:peter.czanik@balabit.com>> Balabit / syslog-ng upstream https://www.balabit.com/blog/author/peterczanik/ https://twitter.com/PCzanik On Sun, Jul 30, 2017 at 7:40 PM, Scheidler, Balázs <balazs.scheidler@balabit.com<mailto:balazs.scheidler@balabit.com>> wrote: Hi, We had a discussion with our Debian maintainer about the fate of syslog-ng-incubator. For those of you who don't know, it is a set of syslog-ng modules not integrated to syslog-ng master for one reason or another. It is available from here: https://github.com/balabit/syslog-ng-incubator The problem with this repository is that it is not really maintained, causing compilation and functionality issues down the line. So our opinion is to go ahead and integrate stuff that can be brough up to speed. Once we've done what we could, we would discontinue the incubator altogether. Please speak up now, if you disagree, but please also be ready to help us out in maintenance in that case. If there are no disagreements in the following week, we would start to phasing out the incubator. We welcome volunteers to: 1) migrate code, OR 2) help with testing If you are the user of any of those plugins, letting us know at this point also helps making sure that no functionality is lost. Thanks. -- Bazsi ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq ________________________________ NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers If you cannot access these links, please notify us by reply message and we will send the contents to you. By communicating with Morgan Stanley you consent to the foregoing and to the voice recording of conversations with personnel of Morgan Stanley.
Hi, Addig one more CC: Laci, who worked on ZMQ. As there are occasional reuests about ZMQ I'd be glad, if ZMQ did not bit rot. Bye, Peter Czanik (CzP) <peter.czanik@balabit.com> Balabit / syslog-ng upstream https://www.balabit.com/blog/author/peterczanik/ https://twitter.com/PCzanik On Wed, Aug 2, 2017 at 9:42 PM, Czanik, Péter <peter.czanik@balabit.com> wrote:
Hi,
As far as I can see, the kafka-c module is definitely in active use. I added Pyr -- the original author of the kafka module -- on CC.
In addition I see once in a while that people are asking about grok and zmq. On the other hand I'm not sure how much functional these modules are (AFAIR the the source part of the ZMQ module was never really finished) and the grok module builds on a C library which is not actively maintained for many years.
I don't recall people mentioning any of the other modules recently.
Bye,
Peter Czanik (CzP) <peter.czanik@balabit.com> Balabit / syslog-ng upstream https://www.balabit.com/blog/author/peterczanik/ https://twitter.com/PCzanik
On Sun, Jul 30, 2017 at 7:40 PM, Scheidler, Balázs < balazs.scheidler@balabit.com> wrote:
Hi,
We had a discussion with our Debian maintainer about the fate of syslog-ng-incubator. For those of you who don't know, it is a set of syslog-ng modules not integrated to syslog-ng master for one reason or another.
It is available from here:
https://github.com/balabit/syslog-ng-incubator
The problem with this repository is that it is not really maintained, causing compilation and functionality issues down the line.
So our opinion is to go ahead and integrate stuff that can be brough up to speed. Once we've done what we could, we would discontinue the incubator altogether.
Please speak up now, if you disagree, but please also be ready to help us out in maintenance in that case.
If there are no disagreements in the following week, we would start to phasing out the incubator.
We welcome volunteers to:
1) migrate code, OR 2) help with testing
If you are the user of any of those plugins, letting us know at this point also helps making sure that no functionality is lost.
Thanks.
-- Bazsi
____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product= syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
Hi, On Sun, Jul 30, 2017 at 07:40:48PM +0200, Scheidler, Balázs wrote:
So our opinion is to go ahead and integrate stuff that can be brough up to speed. Once we've done what we could, we would discontinue the incubator altogether.
Please speak up now, if you disagree, but please also be ready to help us out in maintenance in that case.
I'm speaking up, and I'm ready :-) 1. grok: I really think this module is worth keeping, as it can represent a bridge for logstash users wanting to migrate. The case against being the libgrok maintenance, but I feel it's not too much a risk as the ruby implementation hasn't had updates in years either 2. perl: personal feelings aside ;) I really think this kind of language binding is important to keep, for the same reason as grok: users having perl code lying around in deep dark subdirectories (who doesn't) with useful code can still use it inside syslog-ng. It permits cheap'n'dirty functionality reuse. That being said, we're not using it anymore (at least right now) 3. lua: same for perl, although we never used it. I can help with maintaining the code: we have a gitlab-ci instance, and I can write plumbing to autocompile etc.
participants (4)
-
Czanik, Péter
-
Fabien Wernli
-
Scheidler, Balázs
-
Szalai, Attila