Hi,logstash is basicalli a "translator" for Elastic Search, it's mostly used for parsing an unstructured data source, like a log from syslog and extract all the needed information to feed ElasticSearch with beefy Json.
I think that with plc4x it's a better approach to build the json directly an sent them to Elastic directly, it's pretty easy; achieving the plus of not dealing with an another machine for Logstash.
I think that dropping the support for Elastic is good because not so useful in our scenario.
Regards, S. On 25/01/21 21:55, Christofer Dutz wrote:
Hi all Right now, on Windows machines the build of the logstash plugin seems to work when run in IntelliJ, but fail when run on the commandline. This seems to be a known issue and probably wasn't detected yet as most PLC4X devs don't work on Windows and I just recently started to. Given the Elastic folks recently changed their license to one that is definitely incompatible, if we update, I am not willing to invest time into this and would rather like to remove the logstash support alltogether. What do you think? Chris
OpenPGP_signature
Description: OpenPGP digital signature
