Not that I know of, I talked to a friend of mine who was interested but he's working on a different beat at the moment. In NiFi/MiNiFi the approach has been to get the data from the edge using MiNiFi agents (same place you might drop an Elasticsearch beat), sending back to a NiFi and using PutElasticsearch (using the transport protocol) to get the data into Elasticsearch.
How did you envision a beat being used? I think it would be great to have a Go library for site-to-site communications, then leverage that in a beat or anything else. The beat could ingest from a site-to-site connection and send to ES, for example. Then a MiNiFi agent could simply write to an output port (i.e. not needing to know there's a beat or anything else on the other side) and the beat could do the transport. Having said that, a beat may be faster for this use case but you'd be losing other features/capabilities that NiFi offers such as provenance, replay, etc. Regards, Matt On Fri, Dec 9, 2016 at 10:55 AM, Gaspar, Carson <[email protected]> wrote: > Is anyone working on a beats producer / consumer to integrate with the > Elastic ecosystem? > >
