From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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-ej1-x644.google.com (mail-ej1-x644.google.com [IPv6:2a00:1450:4864:20::644]) (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 32AE61F5B1 for ; Mon, 27 Jul 2020 15:16:03 +0000 (UTC) Received: by mail-ej1-x644.google.com with SMTP id l4so17393326ejd.13 for ; Mon, 27 Jul 2020 08:16:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=natanson-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ovewnfegXqR8mfYhGGmjqDU+LP6D2BhIdEmouiyAlyk=; b=xCJbVEzmYPMPc4+eAD0/9klLiUOAPxWNNUr217rgTIRpwQnUHxNpXHnqE+Saelr9sz Y/0tEIE8wVGDX6yMg411OFm1k5XIIq3qMQznxj/P68TqIsWpELM291w6i82fvoMrTphq jaEybLTj/gWM9ItH27IvDD1CblcIPQnIG/9UeW20EoOv2bQV9hEgAiZdD5BIJvJNKpyS ER/nDAtgaab6x4xaV0qybjdOUi8CPI5kmnizNInypL5OAgdEi8nb3QYS7rV2uTG4fYBu OaV9IDLA9ZQ5i6vt2s+CEwo94HtjDYPwwq8TCsuqO2bUQFHtsP7V2LdaAutuSA/8Kf+e fynw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ovewnfegXqR8mfYhGGmjqDU+LP6D2BhIdEmouiyAlyk=; b=FqM0OvkIVqHxf2EuSoKlOpl84a5aoB94teSIpkZW/+F8ivwcIG2yD5NnJSQWQFO7jO py9vQzbxRQ/yxGmX9xDPcJq3tyRJXF3rwkoQGxMvF7SR+V37GKIobfr3YeLWY+9obqWH wLSsuvPCrv+MEADvqAgCavpRaE+NpOoUYrI2BIahpzWW7Slliy0piXJdxQjWAfI3Xgv2 XZ3BbUsV5P5XONmm3Fjze2ZeoVXDdR/+Hh+P8CdZmKkyq3dzIga+CZ/sNxZcpabwH4fo pbahldoVzmK7N3W5sZgy1Hexb1j5rOd4HTjHXtQezcbxLYlSfJ3m++C7JKNmoCwvfT10 I5GQ== X-Gm-Message-State: AOAM5308jZ1TNjIs4P5oKGzfHI1mePTQisdOZI/KQOXJNv7jnmCaXBtc c3DDaROfkiHckA/quJ+DTvfJdU5rdXT0P4Knbn74iQ== X-Google-Smtp-Source: ABdhPJzlMXgxc8q5VyfD6W6zeboTe0IB0dpkCmtuCgEov3dB6TSub28nBI2YDkNDQD+w0Ai81d8i3EfyNeV/nVY7mMA= X-Received: by 2002:a17:906:13c4:: with SMTP id g4mr15771012ejc.131.1595862960507; Mon, 27 Jul 2020 08:16:00 -0700 (PDT) MIME-Version: 1.0 References: <20200726044647.GA19757@dcvr> In-Reply-To: <20200726044647.GA19757@dcvr> From: Josh Natanson Date: Mon, 27 Jul 2020 11:15:49 -0400 Message-ID: Subject: Re: Clogger request_time formatting To: Eric Wong Cc: clogger-public@yhbt.net Content-Type: text/plain; charset="UTF-8" List-Id: I'm hoping to find some time this week to work on it. What's your preferred way to review? Thanks, - Josh On Sun, Jul 26, 2020 at 12:46 AM Eric Wong wrote: > > Josh Natanson wrote: > > 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. > > Ping. Were you going to work on a patch for this? > I'd be happy to help you review at some point. > > cf. > https://yhbt.net/clogger-public/CAPdx2szjqUuFjUtrgoeXXwmz0HzfdnWe+2h2Sp_ywDkTDVL0-g@mail.gmail.com/t/ > > Thanks.