| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joshua Tolley <eggyknap(at)gmail(dot)com>, jd(at)commandprompt(dot)com, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: syslog_line_prefix |
| Date: | 2009-09-27 21:03:15 |
| Message-ID: | 603c8f070909271403h43826f6bqdd5997860a8d312e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Sep 27, 2009 at 4:54 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On Sun, 2009-09-27 at 16:15 -0400, Tom Lane wrote:
>> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> > Then why not send everything to syslog and have syslog filter it to the
>> > places you want to? That is what syslog is for, after all.
>>
>> We send all syslog output with the same identifier/priority/facility,
>> so there's not a lot of hope of getting syslog to do any useful
>> filtering (at least not with the versions of syslog I'm familiar with).
>
> Time to upgrade then. ;-) For example, the default syslog in Fedora has
> been rsyslog since Fedora 8, and that one can do a lot more than just
> filter by identifier/priority/facility. syslog-ng is another popular
> example for a more featureful syslog.
Presumably csvlog would be good for these sorts of things too, no?
The whole point is it's machine-readable.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2009-09-27 21:47:03 | Re: operator exclusion constraints |
| Previous Message | Peter Eisentraut | 2009-09-27 20:54:37 | Re: syslog_line_prefix |