[rsyslog] FYI: funding rsyslog development

[david at lang.hm]

On Fri, 25 Nov 2011, david at lang.hm wrote:

> On Fri, 25 Nov 2011, Champ Clark III [Quadrant] wrote:
>
>> On Nov 25, 2011, at 11:47 AM, Rainer Gerhards wrote:
>> 
>>> One non-intrusive thing we will try is to create a special version of our
>>> Windows tools and make this work very well with rsyslog. That at least is 
>>> a
>>> way for those guys in big corporations that want to support us can do so 
>>> even
>>> if the company does not understand open source. There is some hope that 
>>> this
>>> works, but it is weak as we already offer these tools and tell folks that
>>> they can use them to help fund the project. Not sure how much more a 
>>> renamed
>>> and somewhat streamlined agent for Windows will bring. Bet let's hope for 
>>> the
>>> best (bottom line: we try to explore unintrusive ways to find new funding
>>> streams).
>
> A good tool to send logs from windows boxes with support would be very 
> useful. there are a number of 'free' tools out there, and some other fairly 
> cheap ones (including from adiscon), but the ones that are pure community 
> projects tend to not keep up with windows releases (and have no support), 
> while the ones from commercial companies are all really intended for other 
> things and just happen to do syslog as well.

one other reason this would be a good idea is that it would clearly 
deliniate the support as being for rsyslog. If the companies were to spend 
the similar amounts of money on the existing adiscon windows agent, the 
company would have no way of knowing that the reason for this was the 
rsyslog support.

As a side note on this, I'm hoping that this rsyslog windows agent could 
be done by grafting a windows eventlog input onto most of the existing 
rsyslog capabilities. It would be great it this was to mean that a lot of 
the existing capabilities were available to logging from windows (relp, 
disk assisted queues, failover if a receiver is down, etc)

David Lang