Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <3CA1F347.8030709@stason.org>
Date: Thu, 28 Mar 2002 00:28:55 +0800
From: Stas Bekman <stas@stason.org>
Organization: Hope, Humanized
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/00200203
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: [Fwd: [PATCH scoreboard] adding port entry]
References: <200203271446.JAA28643@devsys.jaguNET.com>
 <3CA1E575.65C4985C@remulak.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Greg Ames wrote:
> Jim Jagielski wrote:
> 
> 
>>Well, it's kind of easy (and dangerous) to shove too much info into
>>the scoreboard, and cause some nasty overhead... That's the reason why
>>I put some things in the "extended status" area, so that we always
>>have the important stuff available, and the extra stuff only when
>>specifically requested (and people are willing to accept the tradeoff). :)
> 
> 
> But extended status can also get bloated.  In addition to the extra overhead,
> there's the problem of making the display readable.  Looking at
> http://apache.org/server-status, I don't see where the server IP address and
> port would fit comfortably in addition to what's already on the detail lines.  

First of all please remember that mod_status is not the only user of the 
scoreboard, Apache::VMonitor does have a space for vhost :) Of course I 
do realize that users need to enable mod_status and extended status in 
order to get to the extra data. But that's fine.

So there are two different issues here:

1. patching the scoreboard to collect and store this extra info

2. patching mod_status to use this extra info

We can resolve the first issue first and then see how to present this 
info (the second issue).

> A few possibilities come to mind:
> *  stick the ip/port info in the scoreboard, but don't display it in
> mod_status.  
> *  provide a directive that lets you choose between seeing the vhost name or 
>    server IP/port.  I doubt that many folks use both name based vhosts and IP 
>    based vhosts.  Or make such a decision based on the existing vhost
> directives.
> *  provide format strings, like we do for the access logs. (seems like too much
> work)

since mod_status in the extended mode is already doing a lot of work,
how much of an extra overhead will the port/ip info will add?

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com