Thanks, Rob! On Mon, Mar 23, 2015 at 5:18 PM Rob Miller <[email protected]> wrote:
> On 03/23/2015 03:12 PM, Ali wrote: > > Hi, all. > > > > I discovered that our old VMs are not supported by Heka 0.10; CMake is > > too old. > CMake is needed to build Heka, but not to run it. Maybe it's possible for > you to build Heka on a single machine that has CMake 3 or greater and then > move the binaries and libraries to the other machines? > D'oh. I meant glibc is too old. It's 2.5. (I did try to build it first rather than install the pre-built binaries so I did see that CMake is too old also.) > > The only data sources I need right now are log files, but I > > can see that changing as we progress with our Heka implementation. In > > this case, does syslog seem like a good option for sending the data on > > to a remote Heka host? It seems robust enough to handle periods of > > connectivity failures so data won't be lost, but I don't have any > > firsthand experience with this beyond playing around with Logstash for a > > couple months. > > > > I imaged that syslog would watch the local log files and then send their > > events on to Heka's TcpInput. > This is definitely possible, yes. > Great. Just wanted to be sure I wasn't overlooking a more efficient solution. -Ali
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
