logging clusters
| From: | Alex Black | Date: | Fri, 08 Dec 2000 23:34:57 +0000 |
| Subject: | logging clusters | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-29424@lists.php.net to get a copy of this message | ||
hi all,
I wanted to bring up the subject of logging webserver clusters, and see what
people thing the best way to do it is:
-turn off apache logging, and use PHP to log in real-time to a database
(dangerous if you are running a large site, although I suppose you could run
a separate logging Dbserver)
-keep normal apache logs, and have a PHP script which periodically
uploads them to a central admin machine (icky)
-keep normal apache logs, and use a set of cron'd shell scripts to send
them to an admin machine where you run a special admin console that combines
+ analyzes them.
For example, I'd prefer to do all of my access logging to oracle, because I
can can get access to the data and draw charts based on it, etc etc. It also
means I can easily do mass reverse-lookups without having to have apache do
it (which we all know isn't really viable in production)
so......
the only other thing I can think of is to have apache do its logs normally,
and run a php script as a standalone app that connects to oracle, dumps the
contents of the log in, verifies that everything is ok, then deletes the
stuff it took out from the apache log.
that works, but it seems a little funky, especially for systems that have
fairly normal load around-the-clock...
thoughts?
_a
--
Alex Black, Head Monkey
enigma@turingstudio.com
The Turing Studio, Inc.
http://www.turingstudio.com
vox+510.666.0074
fax+510.666.0093
Saul Zaentz Film Center
2600 Tenth St Suite 433
Berkeley, CA 94710-2522