-
Notifications
You must be signed in to change notification settings - Fork 20
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
support stream to bleve #39
Comments
Umm.. this tool is just a pluggable log-router. The log destination depends on what the user will configure. If an user has elastic search setup, then he/she needs to stream to elastic. One cannot just remove elastic as a target. If you are asking to add bleve support, then it's a different issue. Perhaps I have misunderstood something ? |
Since you put it that way then yes I am suggesting adding bleve as a provider. Currently I use the blast GitHub project to cluster bleve. This allows you to log over GRPC and then it's placed on the cluster in a HA setup. The reason I tend to use bleve is because it golang and so less to worry about but also because you can run bleve anyway. In a mobile, on a website. It allows all my edge devices to store and forward the log |
Ok. Just curious though - are you currently using funnel and would like to stream to bleve ? Or is this something that you would like funnel to be able to do ? |
something i would like it to do :) |
Just a pure golang alternative to elastic.
It also means you could index client side in the agent if you wanted to of course.
You can bring up a huge cluster by just denting to S3 or NATS and then let the server side bleve do the indexing and searching also.
It's very easy to get this going to replace elastic since it's just logs.
If you want a sample I can point you to some as others have written log indexers for bless e already
The text was updated successfully, but these errors were encountered: