ProxyPass and common logging

Have you considered HSL (Click Here)? This logs on the wire to a pool defined locally on the LTM so you can have a log farm to handle the load in the event you lose a single server. Alternatively, you can create special log files if you have a particular string in the log message for syslog to key off of and send to alternate file. You could use the virtual name command to specific the appropriate virtual server in the log message from the iRule, then create your files in syslog as such (virtualserver1 as an example):

 

 

tmsh modify sys syslog include '"
filter f_local0 {
    facility(local0) and not match(\": virtualserver1-\");
};
 
filter f_local0_virtualserver1 {
    facility(local0) and match(\": virtualserver1-\");
};
 
destination d_virtualserver1 {
    file(\"/var/log/virtualserver1\" create_dirs(yes));
};
 
log {
    source(local);
    filter(f_local0_virtualserver1);
    destination(d_virtualserver1);
};
"'

tmsh save / sys config
tmsh restart sys service syslog-ng

 

 

Just in case the code gets garbled above, smp wrote a tech tip on custom syslog files and rotation: http://devcentral.f5.com/Tutorials/TechTips/tabid/63/articleType/ArticleView/articleId/1084377/Writing-to-and-rotating-custom-log-files.aspx Click Here

 

 

HTH....Jason