-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
View events from a custom elasticsearch index #83
Comments
Try using |
Thanks. No luck with that option either. It seems like evebox is looking for a template called Here is the log output
|
Ok. What’s the name? EveBox allows for a different name, but expects it to be in the default logstash style. Can you tell me how your differs from the default logstash style? |
Also, see if you can see events under the event tab, it’s a little more forgiving than the inbox. If so, try the —keyword option (or is it —elasticsearch-keyword) and set the value to 'keyword'. |
The template is called The Thanks. |
I renamed the template to
|
Regarding your last comment, Elastic Search can be weird when tweaking things without an index rollover. Sometimes this fixes itself within 24 hours. At least I don't know the proper fix, but this seems to happen. The real fix for this issue is to allow a template name as well as an index name to be specified. Which I will add real soon. |
If you're willing to test, I have a build up here: https://gitlab.com/jasonish/evebox/-/jobs/124323346/artifacts/browse It adds a new command line option, |
Thanks! Will give this a try. I will close this issue for now. Will reopen or reach out if I need help. |
I am running a 6.3.2 ELK stack with logstash sending eve logs to a custom index. When I run the evebox docker container with the
-I
option, specifying the index name, I do not see any events in web interface. Here is the command I am running -Do I need to specify another option, or change one of the options to get evebox to show the events?
BTW, the
oneshot
option works when I send theeve.json
file to evebox.The text was updated successfully, but these errors were encountered: