-
Notifications
You must be signed in to change notification settings - Fork 41
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
Getting Fortidragon to fly with rsyslog #39
Comments
I think we should follow datastreams index strategy instead of
I think we can use
Also, that could reuse the index templates configs. Take into account that I split it even further, by |
I think i followed https://chabik.com/2019/03/rsyslog-to-elasticsearch/ any idea on what to change in the config? I mean still if i understand it corretly it should at least find some feeded values from the elastic index, as rsyslog seems to send its stuff into when i activate it. |
Ok, i must be doing something completely wrong on the rsyslog rule. i am trying to figure out how to change the rule to not use logstash but do directly omelasticsearch |
looks like https://gist.github.com/pando85/75f06fb9a3b67788342e700fa8365674 could help |
I am giving it another try, as time allows now, however still can't get it to work. I think there is some documentation missing for the Elastic/Kibana Setup. |
I am also checking the connection to Grafana Loki, so I am considering using Promtail for that, which might be more efficient because it is not java. We will see how that goes, I will keep eveybody updated. |
My main problem at the moment (as i am not yet experienced at Elastic/Kibana) is to get all the component templates inside of Elastic, is there a "nice" way to import them by the files in the repo? best Regards |
mmmm nice is manual, it takes a while (30 min aprox) but you only got to do it once. Just go into devtools inside kibana and load component templates both from Elastic ECS and FortiDragon specific. Do it manually one by one: https://github.com/enotspe/fortinet-2-elasticsearch#on-kibana |
Tried already, if i try to add /master/index%20templates/component%20templates/logs-fortinet.forticlient%40ilm.json for example it seems to be incomplete and it claims about missing PUT or similar. |
You have to load the ilm policies first |
thx for your help, i created for example the "ilm policy fortigate.traffic" however still as mentioned above, cant do that example in the dev console: { |
We can schedule a time for to help you online. Let me know if that would fine |
Hello @thetuxinator. We have moved all logic away from logstash to Elasticsearch ingest pipelines. That means that you can basically use any log collector/forwarder to receive logs from firewalls and deliver them to Elasticsearch. We use Elastic Agent with UDP input, but Rsyslog will work as well (probably better). Just point the logs to a datastream that calls the ingest pipeline. I will not test Rsyslog tough, I will test Vector but you can go ahead and try Rsyslog. Please share your results if you succeed. |
So i did a fork where i added my README/DOCS for Rsyslog. Maybe you can check if i missed something? See https://github.com/thetuxinator/fortinet-2-elasticsearch-rsyslog/blob/master/README-RSYSLOG.md maybe the "omelasticsearch-rule" is wrong?
regards
The text was updated successfully, but these errors were encountered: