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

Don't drop events that are not whitelisted #28

Open
rajubairishetti opened this issue May 22, 2014 · 2 comments
Open

Don't drop events that are not whitelisted #28

rajubairishetti opened this issue May 22, 2014 · 2 comments
Assignees

Comments

@rajubairishetti
Copy link

Currently, it drops the events that are not white-listed in the scribe conf. This would cause the data loss. Store those events in the local file system to avoid data loss.

@rajubairishetti rajubairishetti self-assigned this May 22, 2014
rajubairishetti added a commit to rajubairishetti/scribe that referenced this issue May 22, 2014
@Amareshwari
Copy link

Does it require to do any code changes? Will configuring default store as
the local file store work?

On Thu, May 22, 2014 at 10:17 AM, rajubairishetti
[email protected]:

Currently, it drops the events that are not white-listed in the scribe
conf. This would cause the data loss. Store those events in the local file
system to avoid data loss.


Reply to this email directly or view it on GitHubhttps://github.com//issues/28
.


The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.

@rajubairishetti
Copy link
Author

No code changes required if we configure a default store.

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

2 participants