RewriteLog and other per-module logging

[Rich Bowen <rb...@rcbowen.com>]

So, I expect it's my own fault for not paying attention to this list  
as closely as I once did, but ...

Losing the ability to have a separate mod_rewrite log file will make  
troubleshooting rewrite stuff so very much more difficult. Is there  
anything planned for the ErrorLog directive that would let me do  
something like:

ErrorLog rewrite:/file/path

so that different modules could have their own log files, in addition  
to their own LogLevel settings?

I certainly see the value of having one combined logging mechanism,  
but having all those messages flowing into a single log file is going  
to increase troubleshooting complexity, and I suspect that folks are  
going to be rather annoyed at the loss of the RewriteLog directive  
without something comparable to replace it.

--
Rich Bowen
rbowen@rcbowen.com

Re: ScriptLog

["Gregg L. Smith" <li...@glewis.com>]

Hi Stefan,

Not in my book it shouldn't go away. It is the only place I can get good 
debug info on perl scripts ... OK, not the only place but it is easiest 
place to find the needed info. Since perl is not 100% dead and gone,
please keep it.  It seems fine as-is, as I've been using it 10 years
now. Please take of radar.

Regards,

Gregg

Stefan Fritsch wrote:
> On Sunday 26 September 2010, Rich Bowen wrote:
>> Another question on this thread - is ScriptLog also going away?
> 
> It hasn't been on my radar so far. Should it?
> 
> pros:
> - per dir config instead of per vhost
> - possibly finer control with different trace levels
> 
> cons:
> - data would use more space in error log because of the log prefix on 
> every line
> - ScriptLogLength would go away, too
> 

Re: ScriptLog

[Rich Bowen <rb...@rcbowen.com>]

On Sep 25, 2010, at 8:08 PM, Stefan Fritsch wrote:

> On Sunday 26 September 2010, Rich Bowen wrote:
>> Another question on this thread - is ScriptLog also going away?
>
> It hasn't been on my radar so far. Should it?
>
> pros:
> - per dir config instead of per vhost
> - possibly finer control with different trace levels
>
> cons:
> - data would use more space in error log because of the log prefix on
> every line
> - ScriptLogLength would go away, too

+1

It would certainly make it easier to document. ;-)

It would be handy for every module to have the same logging methods,  
rather than having an "except for mod_cgi" in the docs.

However, I must admit that I have never (or, at least, not in the last  
decade) used ScriptLog myself much, so perhaps someone who's actually  
used it extensively should weigh in on this.

--
Rich Bowen
rbowen@rcbowen.com

ScriptLog

[Stefan Fritsch <sf...@sfritsch.de>]

On Sunday 26 September 2010, Rich Bowen wrote:
> Another question on this thread - is ScriptLog also going away?

It hasn't been on my radar so far. Should it?

pros:
- per dir config instead of per vhost
- possibly finer control with different trace levels

cons:
- data would use more space in error log because of the log prefix on 
every line
- ScriptLogLength would go away, too

Re: RewriteLog and other per-module logging

[Rich Bowen <rb...@rcbowen.com>]

Another question on this thread - is ScriptLog also going away?

--
Rich Bowen
rbowen@rcbowen.com

Re: RewriteLog and other per-module logging

[Stefan Fritsch <sf...@sfritsch.de>]

On Tuesday 21 September 2010, Rich Bowen wrote:
> On Sep 21, 2010, at 3:01 PM, Stefan Fritsch wrote:
> > I considered that in the beginning but then thought that its
> > usefulness would not outweigh the added complexity. After all,
> > the result is only one grep away:
> > 
> > fgrep '[rewrite:' error_log
> > 
> > or even
> > 
> > tail -f error_log|fgrep '[rewrite:' > rewrite_log
> > 
> > Do you really think that we need this in httpd itself?
> 
> Hmm. You're probably right. This is probably something to "fix in
> documentation" rather than adding the extra complexity. :)

Another thought: If there is demand, we could instead write some piped 
logging helper utility that splits the error log into several files, 
either by module or by level. Maybe even with filtering by regexp.

Re: RewriteLog and other per-module logging

[Rich Bowen <rb...@rcbowen.com>]

On Sep 21, 2010, at 3:01 PM, Stefan Fritsch wrote:

> I considered that in the beginning but then thought that its
> usefulness would not outweigh the added complexity. After all, the
> result is only one grep away:
>
> fgrep '[rewrite:' error_log
>
> or even
>
> tail -f error_log|fgrep '[rewrite:' > rewrite_log
>
> Do you really think that we need this in httpd itself?

Hmm. You're probably right. This is probably something to "fix in  
documentation" rather than adding the extra complexity. :)

--
Rich Bowen
rbowen@rcbowen.com

Re: RewriteLog and other per-module logging

[Stefan Fritsch <sf...@sfritsch.de>]

On Tuesday 21 September 2010, Graham Leggett wrote:
> On 21 Sep 2010, at 4:26 PM, Rich Bowen wrote:
> > So, I expect it's my own fault for not paying attention to this
> > list as closely as I once did, but ...
> > 
> > Losing the ability to have a separate mod_rewrite log file will
> > make troubleshooting rewrite stuff so very much more difficult.
> > Is there anything planned for the ErrorLog directive that would
> > let me do something like:
> > 
> > ErrorLog rewrite:/file/path
> > 
> > so that different modules could have their own log files, in
> > addition to their own LogLevel settings?
> 
> +1.
> 
> While the separate logfile for rewrite was very evil, it was very
> useful to see logging from rewrite in one place.

I considered that in the beginning but then thought that its 
usefulness would not outweigh the added complexity. After all, the 
result is only one grep away:

fgrep '[rewrite:' error_log

or even

tail -f error_log|fgrep '[rewrite:' > rewrite_log

Do you really think that we need this in httpd itself?

Re: RewriteLog and other per-module logging

[Graham Leggett <mi...@sharp.fm>]

On 21 Sep 2010, at 4:26 PM, Rich Bowen wrote:

> So, I expect it's my own fault for not paying attention to this list  
> as closely as I once did, but ...
>
> Losing the ability to have a separate mod_rewrite log file will make  
> troubleshooting rewrite stuff so very much more difficult. Is there  
> anything planned for the ErrorLog directive that would let me do  
> something like:
>
> ErrorLog rewrite:/file/path
>
> so that different modules could have their own log files, in  
> addition to their own LogLevel settings?

+1.

While the separate logfile for rewrite was very evil, it was very  
useful to see logging from rewrite in one place.

Regards,
Graham
--