Received: (qmail 22969 invoked by uid 2012); 3 Jun 1998 11:11:59 -0000 Message-Id: <19980603111159.22968.qmail@hyperreal.org> Date: 3 Jun 1998 11:11:59 -0000 From: Max Flebus Reply-To: max.flebus@comm2000.it To: apbugs@hyperreal.org Subject: Wrong statistics about requests/sec and kB/sec X-Send-Pr-Version: 3.2 >Number: 2343 >Category: mod_status >Synopsis: Status module averages are for entire uptime >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: suspended >Class: change-request >Submitter-Id: apache >Arrival-Date: Wed Jun 3 04:20:01 PDT 1998 >Last-Modified: Thu Jun 4 03:27:02 PDT 1998 >Originator: max.flebus@comm2000.it >Organization: >Release: 1.3b7 >Environment: ALL >Description: The server status figures about requests/sec and kB/sec that are provided by mod_status (GET /Status) are averages for the entire uptime period. Actually I think it is much more interesting to have real-time or near real-time status figures. >How-To-Repeat: Enable mod_status, http://yourserver/status >Fix: >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: coar State-Changed-When: Wed Jun 3 04:56:15 PDT 1998 State-Changed-Why: 'Real-time'? If you want mean figures, you need to have an interval over which the data are collected; what duration would you like? And please let us know a *specific* version of the server with which you're seeing this; "all" isn't acceptable.. Synopsis-Changed-From: Wrong statistics about requests/sec and kB/sec Synopsis-Changed-To: Status module averages are for entire uptime Synopsis-Changed-By: coar Synopsis-Changed-When: Wed Jun 3 04:56:15 PDT 1998 From: MaX Flebus To: coar@apache.org Cc: apache-bugdb@apache.org, apbugs@apache.org Subject: Re: mod_status/2343: Wrong statistics about requests/sec and kB/sec Date: Thu, 04 Jun 1998 10:19:23 +0200 coar@apache.org wrote: > > [In order for any reply to be added to the PR database, ] > [you need to include in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > > Synopsis: Wrong statistics about requests/sec and kB/sec > > State-Changed-From-To: open-feedback > State-Changed-By: coar > State-Changed-When: Wed Jun 3 04:56:15 PDT 1998 > State-Changed-Why: > 'Real-time'? If you want mean figures, you need to have > an interval over which the data are collected; what > duration would you like? A minute... 5 minutes... something like that! Not the full week of uptime I get usually. > And please let us know a *specific* version of the server > with which you're seeing this; "all" isn't acceptable.. I've seen this in 1.3b7 and 1.2.4 but I guess the 'problem' has been there always. > Synopsis-Changed-From: Wrong statistics about requests/sec and kB/sec > Synopsis-Changed-To: Status module averages are for entire uptime I agree... Thank you, MaX State-Changed-From-To: feedback-suspended State-Changed-By: coar State-Changed-When: Thu Jun 4 03:27:02 PDT 1998 State-Changed-Why: Thanks for the additional information. We're closing up 1.3 at the moment (it's frozen), so I'm marking this report for consideration during the next feature cycle. Release-Changed-From-To: ALL-1.3b7 Release-Changed-By: coar Release-Changed-When: Thu Jun 4 03:27:02 PDT 1998 >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]