-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Request to provide a library crate if possible #37
Comments
We don't have such plans so far, but your Redis idea is interesting! I have been thinking about changing |
Thank you for the reply, I guess I will have to wait till you have time to be able to provide a different back end. |
I think we'll be getting there soon. The main obstacle at the moment is figuring out (by having discussions with the compiler) whether Coalesce shout own or mutably borrow the But I am really looking forward to your PR. |
This may allow for more time-intensive enrichment tasks and for different backends (such as Redis mentioned in threathunters-io#37).
This may allow for more time-intensive enrichment tasks and for different backends (such as Redis mentioned in threathunters-io#37).
This may allow for more time-intensive enrichment tasks and for different backends (such as Redis mentioned in threathunters-io#37).
This may allow for more time-intensive enrichment tasks and for different backends (such as Redis mentioned in threathunters-io#37).
This may allow for more time-intensive enrichment tasks and for different backends (such as Redis mentioned in threathunters-io#37).
This may allow for more time-intensive enrichment tasks and for different backends (such as Redis mentioned in threathunters-io#37).
This may allow for more time-intensive enrichment tasks and for different backends (such as Redis mentioned in threathunters-io#37).
The intent is to provide a simple mechanism to allow for alternative backends as discussed in threathunters-io#37.
The intent is to provide a simple mechanism to allow for alternative backends as discussed in threathunters-io#37.
The intent is to provide a simple mechanism to allow for alternative backends as discussed in threathunters-io#37.
The intent is to provide a simple mechanism to allow for alternative backends as discussed in threathunters-io#37.
The intent is to provide a simple mechanism to allow for alternative backends as discussed in threathunters-io#37.
The intent is to provide a simple mechanism to allow for alternative backends (threathunters-io#37) and to get rid of the EOE requirement (threathunters-io#36).
@kushaldas As of 18d38cd (or somewhere around that), there is a library. And in 01866e6, I added a commit that you could use to hook up other backends such as Redis. Can I close this issue? |
@kushaldas laurel 0.2.0 which has just been released is a library crate that happens to also contain the message recoding tool as before. Sorry for taking so long with getting this done… Is this what you had in mind? |
@kushaldas ping? |
@kushaldas I am closing this issue now. |
Missed all notifications in the last 5-6 months, saw this now. Sorry for not replying. I will try again in the coming week and get back to you with any feedback. Thank you for doing this. |
@kushaldas ping? |
Thank you for this useful project.
I am wondering if it will be possible for you to provide a library crate so that other projects can use
laurel
features. This way we don't have to re-invent the wheel and depend onlaurel
as upstream.Use case I am looking at: Instead of logging into a file, push to a redis instance or some other queue for processing in a different way.
The text was updated successfully, but these errors were encountered: