Re: External logging capability

On Mon, 2002-08-12 at 15:35, Henrik Nordstrom wrote:
> On Monday 12 August 2002 21.14, Florin Andrei wrote:
>
> > What's the status of the "External logging capability" module?
>
> Needs to be reviewed.. I am a bit dubious on how well it will handle
> high loads or if the log daemon gets blocked causing the IPC
> connection to fill up..

If that happens, older messages in the queue should be simply
overwritten, right? This should not get the main daemon blocked.

> > Is it going to be included in 2.5?
>
> No.

Ahh... Too bad.

> > My understanding is, this module is the way to do logging into a
> > SQL server, and i'm still looking forward for this feature.
>
> Correct.

Well, Squid is a very serious contender in the arena of HTTP proxies
(yeah, i'm preaching to the converted :-D). When including it in an
enterprise deployment, one would like to do things like logs aggregation
and stuff like that, for various reasons (security, network management,
etc.).
Having a SQL logging mechanism could help these things somehow. Having a
flexible and perhaps modular logger in Squid could help a lot.

I am simply amazed by how bad things are when it comes to logging, and
that's not just Squid.
syslog is ridiculous. Having only flat-text capabilities in every daemon
is ridiculous. We're like in the Stone Age.
That's why i'm so interested in a more powerful and flexible logging
mechanism in Squid.

-- 
Florin Andrei
"In my view, a man's value does not depend on what he learns,
or his position or fame, or what he does, but on what he is
and inwardly becomes." - Sri Aurobindo, a note to his biographers