search

swordzjj / eventlog-to-syslog

Automatically exported from code.google.com/p/eventlog-to-syslog
0 stars 0 forks source link

RFC3195 compliant? #9

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Is eventlog-to-syslog RFC3195 compliant? Meaning - can the service be 
configured to forward the events with TCP instead of UDP? 

Thanks in advance

Regards 
Claus

Original issue reported on code.google.com by cbhaa...@gmail.com on 8 Jul 2010 at 1:07

GoogleCodeExporter commented 8 years ago 
Hi Claus,
Unfortunately the utility is not yet RFC3195 compliant. Adding this support is 
on the roadmap, but I do not have a timeline for it. It will be added once time 
permits.

Sherwin

Original comment by sherwin....@gmail.com on 8 Jul 2010 at 2:12

GoogleCodeExporter commented 8 years ago 
Hi Sherwin,

Any update as to the timeline on configuring UDP/TCP?

Thanks,

Greg

Original comment by gfango...@gmail.com on 14 Sep 2010 at 3:40

GoogleCodeExporter commented 8 years ago 
Sorry for the delayed response Greg. I still do not have a timeline for the TCP 
update. I am in the process of switching work projects so this has gotten put 
on hold. If all goes well within the next few weeks I may be able to provide 
some better news then, but things are a bit uncertain at the moment until 
things settle down on my end.

Original comment by sherwin....@gmail.com on 20 Sep 2010 at 4:01

GoogleCodeExporter commented 8 years ago

Original comment by sherwin....@gmail.com on 29 Nov 2010 at 7:22

GoogleCodeExporter commented 8 years ago 
Issue 17 has been merged into this issue.

Original comment by sherwin....@gmail.com on 29 Nov 2010 at 7:22

GoogleCodeExporter commented 8 years ago 
For those following this issue, I am actively working on adding TCP support. I 
have a test candidate working that should be available for testing in a few 
weeks for those who would like to. Contact me if you would like to test it out 
before hand.

-Sherwin

Original comment by sherwin....@gmail.com on 23 Feb 2011 at 5:14

GoogleCodeExporter commented 8 years ago 
I'm very interested to test TCP support.

Original comment by secsy...@gmail.com on 4 Mar 2011 at 9:39

GoogleCodeExporter commented 8 years ago 
The TCP support I have implemented will not be RFC3195 compliant as that does 
not appear to have wide adoption and is overly complex for very little benefit. 
It will just be simple TCP support for sending messages over TCP instead of 
UDP. I am thinking of adding support for rsyslog's RELP in the future. I will 
issue a beta client in a few weeks with the simple TCP support.

Original comment by sherwin....@gmail.com on 8 Mar 2011 at 5:37

GoogleCodeExporter commented 8 years ago 
FWIW, I would be VERY interested in rsyslog RELP support.  Message reliability 
and encryption are our two largest concerns.

Original comment by esch...@gmail.com on 8 Mar 2011 at 10:32

GoogleCodeExporter commented 8 years ago 
As is mine,  I would very much like to help you test this.  Great work!

Original comment by camu...@gmail.com on 19 Mar 2011 at 3:42

GoogleCodeExporter commented 8 years ago 
I have included preliminary TCP support in the latest release. To enable it, 
simply set the EnableTcp registry key to 1.

Please note this feature is EXPERIMENTAL. I would only recommend using it on a 
test system. If you encounter any issues please let me know. Again this support 
is NOT PRODUCTION READY, and I cannot accept any responsibility for damages 
that may arise from such use.

Thanks,

Sherwin

Original comment by sherwin....@gmail.com on 13 Apr 2011 at 4:12

GoogleCodeExporter commented 8 years ago 
Can anyone report on the reliability of this current implementation?

Original comment by rojaro@gmail.com on 28 Sep 2011 at 5:37

GoogleCodeExporter commented 8 years ago 
The TCP implementation works. However if the service cannot make a handshake, 
the service fails and stops. Could we have the ability to control the timeout 
before the service fails.

Another concern is we do not want our logging server to stop getting logs, so 
could we have the service write a warning to the eventlog and try to handshake 
again?

Original comment by kirkusma...@gmail.com on 5 Oct 2011 at 9:15

GoogleCodeExporter commented 8 years ago 
I am also very interested in this feature.
This is the single and primary reason we cant use eventlog-to-syslog right now, 
which is unfortunate.
For us also, message reliability and encryption are mandatory.
Looking forward in seeing RELP support.

Original comment by Dany.Cos...@aplanos.ca on 14 Jun 2012 at 4:51

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I just installed eventlog to syslog.  I am glad to do any testing you need.  
Lewis

Original comment by lewi...@mail.usf.edu on 9 Jul 2013 at 11:14

GoogleCodeExporter commented 8 years ago 
We would be more than happy to assist with testing tcp/ssl in this application. 
 Again, that feature is all that prevents us from implementing this.

Original comment by sh...@southernfamily.ca on 4 Nov 2013 at 4:54