From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1369 Path: news.gmane.org!not-for-mail From: Charlie Brady Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: svlogd / multilog -> SQL database Date: Thu, 11 Jan 2007 11:50:37 -0500 (EST) Message-ID: References: <5422d5e60701040842ta6e8de3v615d07b6fadea37d@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: sea.gmane.org 1168534280 28277 80.91.229.12 (11 Jan 2007 16:51:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 11 Jan 2007 16:51:20 +0000 (UTC) Cc: supervision@list.skarnet.org Original-X-From: supervision-return-1605-gcsg-supervision=m.gmane.org@list.skarnet.org Thu Jan 11 17:51:09 2007 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.50) id 1H5383-0006bf-4s for gcsg-supervision@gmane.org; Thu, 11 Jan 2007 17:50:15 +0100 Original-Received: (qmail 1410 invoked by uid 76); 11 Jan 2007 16:50:33 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 1403 invoked from network); 11 Jan 2007 16:50:33 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: charlieb.ott.istop.com X-X-Sender: charlieb@e-smith.charlieb.ott.istop.com Original-To: Daniel Clark In-Reply-To: <5422d5e60701040842ta6e8de3v615d07b6fadea37d@mail.gmail.com> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1369 Archived-At: On Thu, 4 Jan 2007, Daniel Clark wrote: > Has anyone happened to have done any work to get svlogd/multilog data > into a SQL database, such as PostgreSQL? I think what you mean to say is, has anyone written a logger which can be used by supervise/runit in place of svlogd/multilog. It will read from standard input, and write log records into an SQL database. I don't see where or why you'd use svlogd or multilog in that scenario. [I'd be concerned about reliability and load issues.] Alternatively, you might post-process svlogd log files into SQL (at normal log rotation time, and from time to time otherwise), depending on what analysis capabilities you are seeking.