Bug#655852: polipo: Polipo should log queries/fetches.

[Rolf Leggewie]

On Sat, 14 Jan 2012 22:01:44 +1100 Donovan Baarda
a...@minkirri.apana.org.au wrote:
 Package: polipo
 Version: 1.0.4.1-1.1
 Severity: wishlist
 
 Dear Maintainer,
 
 I'm used to using squid and using its logs to generate stats useful
 for analysing traffic and proxy performance. This has been very useful
 for tuning cache perfomance and identifying popular and/or problematic
 servers.

https://github.com/jech/polipo/pull/35


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#655852: polipo: Polipo should log queries/fetches.

[Juliusz Chroboczek]

tags 655852 +wontfix
thanks

 With polipo, even with logLevel=0xff there doesn't seem to be any
 sort of query and/or fetch logging output

This is deliberate -- Polipo's upstream author doesn't want to
encourage you to spy on your users.  He believes that logging every
request going through the proxy is an intolerable invasion of users'
privacy, and that a competent administrator should be able to work out
issues without the need for such extensive logging.

-- Juliusz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#655852: polipo: Polipo should log queries/fetches.

[Donovan Baarda]

Package: polipo
Version: 1.0.4.1-1.1
Severity: wishlist

Dear Maintainer,

I'm used to using squid and using its logs to generate stats useful
for analysing traffic and proxy performance. This has been very useful
for tuning cache perfomance and identifying popular and/or problematic
servers.

With polipo, even with logLevel=0xff there doesn't seem to be any sort
of query and/or fetch logging output, making it impossible to do any
sort of analysis.

It would be nice if polipo logged client requests and upstream
fetches. Copying squids logging output would make it easier to use
existing log analyser scripts, but I suspect that squids logging is
actually not that useful for polipo. Even just being able to see
requests/bytes/latency for client requests and upstream fetches would
be useful to determin overall cache hit rates and performance would be
useful.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages polipo depends on:
ii  dpkg  1.16.1.2
ii  install-info  4.13a.dfsg.1-8
ii  libc6 2.13-24

polipo recommends no packages.

polipo suggests no packages.

-- Configuration Files:
/etc/polipo/config changed:
proxyAddress = 0.0.0.0# IPv4 only
allowedClients = 127.0.0.1, 192.168.0.0/24

proxyName = proxy.localnet
proxyPort = 3128
chunkHighMark = 268435456
objectHighMark = 65536
disableIndexing = false
disableServersList = false
dnsQueryIPv6 = no
logSyslog = true
logFacility = daemon
logLevel = 0xFF


-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org