From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <josh@natanson.net>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-3.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE shortcircuit=no
	autolearn=ham autolearn_force=no version=3.4.2
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id CE7AC1F5AE
	for <clogger-public@yhbt.net>; Thu,  9 Jul 2020 16:30:25 +0000 (UTC)
Received: by mail-ed1-x52f.google.com with SMTP id z17so2306975edr.9
        for <clogger-public@yhbt.net>; Thu, 09 Jul 2020 09:30:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=natanson-net.20150623.gappssmtp.com; s=20150623;
        h=mime-version:from:date:message-id:subject:to;
        bh=LvXF3YDmfL6vegoYuO+CmghfpfNkt/4Wcv3dOC4WdDE=;
        b=exgWMHw4gu0ZwuV8cpJl7Kldlp+FfUBgN1bWYfp5G5PYm1MU9dokfribMRTNNwOpcm
         RwnXZTKVnqnJt0EK7nzQnW2+8qOKBGAzut3wyC2W4nmbz4/XL8VcD98tyre7vuAbZx6a
         LQxfcRXbOKHIjJVEOdC5jtUXf/5z62Ja7EMxI1A8wxp/p2xlY4eX7049JTi/J/iYWSLu
         myKG6R4DwCt8qL00ArhXq1LAkOVp/6CqjMg2MCK16eUSJWfcTTqp36rp4DeFyfifTzwP
         wts++7ZaHKPj4H4NHQztcJciclsaVCI5l+UF6eWvnbk4Tutoc7fdETk+Pxw2qxh3tgDM
         zYLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=LvXF3YDmfL6vegoYuO+CmghfpfNkt/4Wcv3dOC4WdDE=;
        b=W8UCsQXKDuSwhNGuj1o+X9cAhEfwUkb8ff+0A4B2rrDNj/1dzbs5cjcBWUprc+fNUj
         fMPHNE9V0221hYIqnZ41wmhO/BAUjK2s9FgYoL/BsPOv/LDCHMK5K08mxw0yCasxxA8E
         ZMV+VHOeA35+0JZoEPilneHVlg3bpN8dLaNU+NfvIjHen+UMMVKX8nufdPPUJ8/wBwZJ
         HjFB4D93VOfT9/lgWqcm3olWUbwwwuTelcLZhhb9TGv2/4Wk7AQbaY8A3kr3C9+FIRwI
         ZzANKcHyoDspbJHr/znl8JPGt5ZVUmWKRO16tT50gF78oPmMoD3Kd57OSWe07aI+hf7G
         UK5A==
X-Gm-Message-State: AOAM5320HG0e0ybV4LBb0ZkcvSdtm12EzRV+O9V/FHD9wRrb2nFicYZ/
	ZkrcDU1eiI3ogz0limfyDwg0mTtpOyzERuNnTlcvn/MMweuDDA==
X-Google-Smtp-Source: ABdhPJwnHlr42YowSDCXdXCB5+Gvwwf+QXaZRizPrtcqCV7EvYd0NLnGwDGR1cWiqCgvb9+b+LFiPEu2q7Cu+ASTZhk=
X-Received: by 2002:a50:fd84:: with SMTP id o4mr53302094edt.117.1594312224001;
 Thu, 09 Jul 2020 09:30:24 -0700 (PDT)
MIME-Version: 1.0
From: Josh Natanson <josh@natanson.net>
Date: Thu, 9 Jul 2020 12:30:12 -0400
Message-ID: <CAPdx2szjqUuFjUtrgoeXXwmz0HzfdnWe+2h2Sp_ywDkTDVL0-g@mail.gmail.com>
Subject: Clogger request_time formatting
To: clogger-public@yhbt.net
Content-Type: text/plain; charset="UTF-8"
List-Id: <clogger-public.yhbt.net>

Hi,

I'm looking to use clogger for some access logging, and I need to
match a legacy format within my organization.  I've managed to
recreate everything I need to, with one exception.  $request_time
looks like it returns seconds, and I need to display microseconds.  I
see that precision is supported, but I haven't been able to figure out
a way to change the actual format.

My questions are: Is there a way to do this that I'm not aware of?  If
not, could it be added?  I can try to take a crack at it if you think
it's a good idea.

Thanks a lot,

- Josh