Dear Sensei users,An update on broken Elasticsearch indices:After digging together with users who have reported the issue, it looks like the indices were broken because some index file integrity got broken. This is usually because of abrupt shutdown of the firewall. If power goes off suddenly, before Elastic does a full write of its in-memory buffers, than we have a broken index.So, not to experience this issue try to turn off your system gracefully. If in any case this happens, Sensei 0.8.0.beta6 has a "Fix Elastic indices" button under Sensei -> Configuration -> Reporting & Data menu. Just click on the button and Sensei will reset only the broken indices. 0.8.0.beta6 is available for update for 0.8 users. 0.8 looks stable enough to offer as an update for existing 0.7 installations. If we do not see any outstanding issues, we'll move 0.8 to the general repo in a few days.
Hello Murat,is there an option to sync/export the collected data to another ELK Stack ?Background: I´m already running a ELK Stack in my network and i want to add the Sensei Data to it,too.Sensei has much more information than the default syslog infos from OPNSense.
SunnyValley evaluating lightweight backend database engines to provide a lighter version for home users with low spec hardware. When they are ready, there will not be a need of such swap tricks...
Archanfel80 could you please make a step by step guide? I will try Sensei on my apu2c4...thank you!
Quote from: mayo on March 30, 2019, 12:32:18 pmArchanfel80 could you please make a step by step guide? I will try Sensei on my apu2c4...thank you!Hi!On a 2c4 which have 4GB ram enough to use the default 2GB swap file. Just enable in the system-miscellaneous.Make sure you have limited Sensei to 100 user maximum, and you have no problem.