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

Request to provide a library crate if possible #37

Closed
kushaldas opened this issue Oct 15, 2021 · 9 comments
Closed

Request to provide a library crate if possible #37

kushaldas opened this issue Oct 15, 2021 · 9 comments

Comments

@kushaldas
Copy link

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 on laurel 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.

@hillu
Copy link
Collaborator

hillu commented Oct 15, 2021

We don't have such plans so far, but your Redis idea is interesting!

I have been thinking about changing Coalesce so that it emits messages to an io::Write interface instead of passing them back to the main loop. Once this is done, I'd be very happy to add other backends in addition to the existing file logger.

@kushaldas
Copy link
Author

We don't have such plans so far, but your Redis idea is interesting!

I have been thinking about changing Coalesce so that it emits messages to an io::Write interface instead of passing them back to the main loop. Once this is done, I'd be very happy to add other backends in addition to the existing file logger.

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.

@hillu
Copy link
Collaborator

hillu commented Oct 16, 2021

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 std::io::Write thing. :-)

But I am really looking forward to your PR.

hillu added a commit to hillu/laurel that referenced this issue Nov 1, 2021
This may allow for more time-intensive enrichment tasks and for
different backends (such as Redis mentioned in threathunters-io#37).
hillu added a commit to hillu/laurel that referenced this issue Nov 1, 2021
This may allow for more time-intensive enrichment tasks and for
different backends (such as Redis mentioned in threathunters-io#37).
hillu added a commit to hillu/laurel that referenced this issue Nov 1, 2021
This may allow for more time-intensive enrichment tasks and for
different backends (such as Redis mentioned in threathunters-io#37).
hillu added a commit to hillu/laurel that referenced this issue Nov 2, 2021
This may allow for more time-intensive enrichment tasks and for
different backends (such as Redis mentioned in threathunters-io#37).
hillu added a commit to hillu/laurel that referenced this issue Nov 22, 2021
This may allow for more time-intensive enrichment tasks and for
different backends (such as Redis mentioned in threathunters-io#37).
hillu added a commit to hillu/laurel that referenced this issue Dec 8, 2021
This may allow for more time-intensive enrichment tasks and for
different backends (such as Redis mentioned in threathunters-io#37).
hillu added a commit to hillu/laurel that referenced this issue Dec 9, 2021
This may allow for more time-intensive enrichment tasks and for
different backends (such as Redis mentioned in threathunters-io#37).
hillu added a commit to hillu/laurel that referenced this issue Dec 9, 2021
The intent is to provide a simple mechanism to allow for alternative
backends as discussed in threathunters-io#37.
hillu added a commit to hillu/laurel that referenced this issue Dec 9, 2021
The intent is to provide a simple mechanism to allow for alternative
backends as discussed in threathunters-io#37.
hillu added a commit to hillu/laurel that referenced this issue Dec 9, 2021
The intent is to provide a simple mechanism to allow for alternative
backends as discussed in threathunters-io#37.
hillu added a commit to hillu/laurel that referenced this issue Dec 9, 2021
The intent is to provide a simple mechanism to allow for alternative
backends as discussed in threathunters-io#37.
hillu added a commit to hillu/laurel that referenced this issue Dec 10, 2021
The intent is to provide a simple mechanism to allow for alternative
backends as discussed in threathunters-io#37.
hillu added a commit to hillu/laurel that referenced this issue Dec 10, 2021
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).
hillu added a commit that referenced this issue Dec 10, 2021
The intent is to provide a simple mechanism to allow for alternative
backends (#37) and to get rid of the EOE requirement (#36).
@hillu
Copy link
Collaborator

hillu commented Dec 10, 2021

@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?

@hillu
Copy link
Collaborator

hillu commented Dec 20, 2021

@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?

@hillu
Copy link
Collaborator

hillu commented Dec 25, 2021

@kushaldas ping?

@hillu
Copy link
Collaborator

hillu commented Jan 23, 2022

@kushaldas I am closing this issue now.

@hillu hillu closed this as completed Jan 23, 2022
@kushaldas
Copy link
Author

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.

@hillu hillu reopened this Apr 23, 2022
@hillu
Copy link
Collaborator

hillu commented May 30, 2022

@kushaldas ping?

@hillu hillu closed this as completed Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants