Date: Mon, 7 Aug 2017 09:08:51 -0600 From: markham breitbach <markham@ssimicro.com> To: freebsd-questions@freebsd.org Subject: Re: log centralizer? Message-ID: <9f579c0e-c894-33f3-9c44-bab2eb42850b@ssimicro.com> In-Reply-To: <CACcSE1xP0c8yA44LLwTfX2nWWBqJf=VEgR07TbqmZwKTaLCd%2Bw@mail.gmail.com> References: <CACcSE1xP0c8yA44LLwTfX2nWWBqJf=VEgR07TbqmZwKTaLCd%2Bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If all you want to do is collect the logs and you are fine with the CLI, there is no reason you can't do this with BSD syslog.=20 Depending on how you want to organize your logs, you may want to look at rsyslog or syslog-ng for some more powerful filtering rules. Splunk is so much more than just a fancy graphical interface though! -Markham On 2017-08-06 11:39 PM, Aleksandr Miroslav wrote: > I'm looking for a mechanism to collect and store all logs into a > centralized location. I'm not looking for a fancy graphical interface > (a la Splunk) to search those logs just yet, just collecting them on a > centralized server is fine for the moment. > > Is there something available in ports/base that I can use for this > purpose? I took a quick look at ELK, it seems overly complicated, but > iIve never used it. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd= =2Eorg"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9f579c0e-c894-33f3-9c44-bab2eb42850b>