Quite true. There are a couple of approaches to take to
this. pen (http://siag.nu/pen/) implements several of them
and might be a good place to steal ideas/code. pen has:
mergelogs: A script to merge pen's log file with Apache's
log files to produce a "corrected" log file
penlog/penlogd: A client/server combo to do the same thing
in real time. See the release notes for pen 0.9.0.
-H flag: A flag to add a X-Forwarded-For header to HTTP
requests.
The other option, taken by some commercial load balancers,
is to rewrite packets bound for the back end servers such
that the packets have the actual client's source address.
The client continues to send traffic through the load
balancer but return traffic flows directly back to the
client. This aleviates the need to do special log handling,
but introduces plenty of its own issues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-08-12
Logged In: YES
user_id=487247
You could always have distributor write its own logs in Apache
format. Just a thought.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-08-12
Logged In: YES
user_id=487247
Rewriting the packets would also alleviate a great deal of the
traffic on the load balancer, but it would seriously break SSL
(among other things).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=215973
Quite true. There are a couple of approaches to take to
this. pen (http://siag.nu/pen/) implements several of them
and might be a good place to steal ideas/code. pen has:
mergelogs: A script to merge pen's log file with Apache's
log files to produce a "corrected" log file
penlog/penlogd: A client/server combo to do the same thing
in real time. See the release notes for pen 0.9.0.
-H flag: A flag to add a X-Forwarded-For header to HTTP
requests.
The other option, taken by some commercial load balancers,
is to rewrite packets bound for the back end servers such
that the packets have the actual client's source address.
The client continues to send traffic through the load
balancer but return traffic flows directly back to the
client. This aleviates the need to do special log handling,
but introduces plenty of its own issues.
Logged In: YES
user_id=487247
You could always have distributor write its own logs in Apache
format. Just a thought.
Logged In: YES
user_id=487247
Rewriting the packets would also alleviate a great deal of the
traffic on the load balancer, but it would seriously break SSL
(among other things).