[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hockeypuck logging
From: |
Andrew Gallagher |
Subject: |
Re: Hockeypuck logging |
Date: |
Thu, 16 Sep 2021 11:52:49 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Betterbird/91.1.0 |
On 15/09/2021 18:44, Skip Carter wrote:
But MY logs look like:
INFO[169329]
lookup fp=63af7aa15067c05616fddd88a3a2e8f
226f0bc06 length=1219 op=get
INFO[169329] GET=/pks/lookup?op=ge
t&options=mr&search=0x63AF7AA15067C05616FDDD88A3A2E8F226F0BC06
duration=6.444816ms from=20.186.38.99:1088 host=50.242.82.152:11371 status-
code=200 user-agent=pgp-happy-eyeballs
INFO[169503] GET=/pks/lookup?op=st
ats duration=819.389µs from=188.141.23.154:54922
host=keyserver.taygeta.com:11371 status-code=200 user-agent=sks_peers/0.2 (SKS
mesh spidering)
The syslog format is much more useful. Where can I find documentation on
customizing the logging ? Pushing the logs to syslog would be preferable, but
even just adusting the format would be helpful
* How are you running hockeypuck?
* Is 169329 the hockeypuck process ID?
* Where do you see these logs?
* Have you tried sending stdout/stderr to `| logger -t hockeypuck` ?
A
OpenPGP_0xFB73E21AF1163937.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature