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

Evtsys cache #13

Closed
GoogleCodeExporter opened this issue Apr 27, 2015 · 1 comment
Closed

Evtsys cache #13

GoogleCodeExporter opened this issue Apr 27, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Is possible to add the ability to keep the logs stored in cache in case of fail 
of the centralize syslog server?

Many thanks 

Roberto 

Original issue reported on code.google.com by roberto....@gmail.com on 31 Aug 2010 at 5:37

@GoogleCodeExporter
Copy link
Author

Hi Roberto, thanks for your interest in the utility. Unfortunately I do not see 
any plans for this in the future. It would require some rewriting and overhead 
from the utility which I do not see a very good use case for. The reason I 
implemented the duplicate log server ability was so we could mitigate just such 
a problem.

Maintaining a separate cache would require file checking, specifying limits, 
memory and process overhead and kind of moves away from the simplicity I'm 
trying to maintain. Remember this was geared originally toward very busy 
servers, so I prefer to keep any utility processing to just what's required. 
Additionally, since I'm only using UDP currently there would be no way to 
determine whether a message arrived or not so the cache would be kept 
permanently.

What you could do in the event of a known syslog server failure is backup all 
of the windows logs to a remote machine so that you can maintain the remote 
backups. I can provide powershell scripts capable of doing this remotely if you 
like.

-Sherwin

Original comment by sherwin....@gmail.com on 10 Sep 2010 at 12:57

  • Changed state: WontFix
  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

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

No branches or pull requests

1 participant