This is to announce the release of Pound v2.2.6. Changes in this version
(since 2.2.5):

Enhancements:
  - added transaction time logging to LogLevel 5
  - added priority display for poundctl

Bug fixes:
  - fixed problem when adding session via poundctl
  - fixed problem in session dump to poundctl (to show correct back-end)
  - fixed problem in kill_be call to t_clean (fixes failed connects)

The software is at version 2.2.6 (beta quality). Further testing
(especially under heavy loads), improvements and suggestions are
welcome.[...]

I wrote a small awk script to give me statistics on load balancing, and 
average time of response for each service.  I thought it might be useful 
for others (and my way of giving something back to pound).  The script 
outputs the total number of requests made to your pound server, the 
slowest response time, and average response time.  Then for each Service 
& Backend, it prints the number of requests, the slowest response time 
for that Service->Backend, and average time.

This script is written for LogLevel 5 (pound 2.2.6), and assumes that 
the syslog prefix has been stripped already (meaning only what pound 
logs).  It assumes that all your backend IP addresses start with "192" 
(you can comment out that line or make appropriate changes). Its also 
much more useful if you give each of your Services a name. 


BEGIN {
FS=" "
OFS="\t"
}
{
  //get service name (strip the opening parenthesis from the name)
  svc=$(NF-4)
  svc=substr(svc,2,length(svc))

  //get the backend address (strip the closing parenthesis)
  be=$(NF-2)
  sub(")", "", be)

  beTime=$(NF-1)
  //use the info for backends with ip 192.*
  if (index(be,"192") == 1) {
        entry=svc "\t->\t" be
        totRequests[entry]++
        reqTime[entry]+=beTime
        if (beTime > maxTime[entry])
                maxTime[entry]=beTime
        totalTime+=beTime
        if (beTime > maxTotalTime)
                maxTotalTime=beTime
  }
}
END {
  print "total", NR, maxTotalTime, totalTime/NF
  for (entry in totRequests)
      print entry , totRequests[entry], maxTime[entry], 
reqTime[entry]/totRequests[entry]
}

found a small bug in the END, it should be
print "total", NR, maxTotalTime, totalTime/NR
instead of
print "total", NR, maxTotalTime, totalTime/NF

Albert wrote:[...]

Robert Segall wrote:[...]

I've attached a diff for LogLevel 6 - same as 5 but with vhost 
information.  Any chance it, or something similar, can go in?

Regards,[...]

Dave Steinberg wrote:[...][...][...]

Um, just kidding... attached...  :)

Regards,[...]

>> Robert Segall wrote:
>>> This is to announce the release of Pound v2.2.6. Changes in this
version
>>> (since 2.2.5):
>>>
>>> Enhancements:
>>>   - added transaction time logging to LogLevel 5
>>>   - added priority display for poundctl[...][...]

Sorry for the confusion - looks like the attachment is getting stripped 
by the list (yet, it appears in the archives).

You can access the patch via the list archives or here:

http://www.redterror.net/patches/pound-loglevel6.diff

Regards,[...]

>>> Robert Segall wrote:
>>>> This is to announce the release of Pound v2.2.6. Changes in
this
>>>> version
>>>> (since 2.2.5):
>>>>
>>>> Enhancements:
>>>>   - added transaction time logging to LogLevel 5
>>>>   - added priority display for poundctl
>>>
>>> I've attached a diff for LogLevel 6 - same as 5 but with vhost
>>> information.  Any chance it, or something similar, can go
in?[...][...]

FYI, attachments on this list can always be found in the list archives,
the link is at the bottom of every mail.

Simon
[...]

On Sun, 2007-03-04 at 22:33 -0500, Dave Steinberg wrote:[...]

Thanks Dave. Quick informal poll here: does it make more sense to add a
new log level, or to integrate the vhost in LogLevel 5?[...]

Robert Segall wrote:[...][...]
>>> This is to announce the release of Pound v2.2.6. Changes in this
version
>>> (since 2.2.5):
>>>
>>> Enhancements:
>>>   - added transaction time logging to LogLevel 5
>>>   - added priority display for poundctl
>>>       [...][...]
I'm using LogLevel 5, and I wouldn't mind having vhost in it.

Robert,

We'd definitely use vhost in LogLevel 5, since each of our users has  
their own vhost.

Regards,
-Nathan / PBwiki

On Mar 5, 2007, at 10:21 AM, Robert Segall wrote:
[...][...]
>>> This is to announce the release of Pound v2.2.6. Changes in this  
>>> version
>>> (since 2.2.5):
>>>
>>> Enhancements:
>>>   - added transaction time logging to LogLevel 5
>>>   - added priority display for poundctl[...][...]

Hi,
[...][...]

What's about an option to affect the log-entry like the apache
LogFormat-directive? Or is this oversized?

Regards,

Falk

On Mon, 2007-03-05 at 21:10 +0100, Falk Brockerhoff wrote:[...]

Sorry, I'm rather allergic to that. Parsing strings is never fun, and
quite often a rich source of problems.[...]

> This is to announce the release of Pound v2.2.6. Changes in this
version[...]

In case consensus wasn't building around adding vhost to log level 5 - 
attached is a patch for log level 6 that actually works.

Nice job on my part to lose 2 days worth of logs.  Sigh...

PS - I promise I won't post 5 messages trying to get the attachment 
through.  :)

Regards,[...]

This is to announce the release of Pound v2.2.7. Changes in this version
(since 2.2.6):

Enhancements:

- dynamic scaling is now a configuration directive (DynScale), which can
be set either globally or at the Service level. By default it is OFF.

- added vhost to LogLevel 5

The software is at version 2.2.7 (beta quality). Further testing
(especially under heavy loads), improvements and suggestions are
welcome.[...]