Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118866 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 63758 invoked from network); 21 Oct 2022 10:45:55 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 21 Oct 2022 10:45:55 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 498B218050B for ; Fri, 21 Oct 2022 03:45:54 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wm1-f46.google.com (mail-wm1-f46.google.com [209.85.128.46]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 21 Oct 2022 03:45:53 -0700 (PDT) Received: by mail-wm1-f46.google.com with SMTP id c3-20020a1c3503000000b003bd21e3dd7aso4721115wma.1 for ; Fri, 21 Oct 2022 03:45:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=yq3GD6f9n+ATIN7/KMdwx5RwvdA/RUahPhQ2ohYpgSM=; b=fnbDg0gonf/KPcgbWYehj0YMVyznXrG4AD8mdcy56LZdzVmYS8ws5+Vcq6XcmOPjP/ zUs/zCVLPDxdm2Ajw4o5bVvkG1nzsc2aql0BxoK1Ct7nxRBQOR+MMik6zZc+8RAylZU9 pjaofxn7FADNyW+kicLyTMtTOcxbBcgf35rubXVFoHaMD9EINKULrsTPYCzWLfbyfWYI iUEIrpfHRDduL6p11A1TBKFrKLFmRsyGztu7i6qvwHnVHxZJk44uF+HRLc4z1lyTW7Y0 wBPIKeYM9uC3yKSr2zXE/Ha5ALuVMx6nbwroWlp0fv768T25UpTi0ULpSFvivL9+pk2p 10Kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=yq3GD6f9n+ATIN7/KMdwx5RwvdA/RUahPhQ2ohYpgSM=; b=mQJPxkxqHZrlGIsHaPpT9arQ7+dpnG34Ciq4FWs+G71kWKFaXKJeXUJqSN+Ylk/uE5 MXV/7Z0FH7stK4CxC45g028onqNwD2k9dWvjmqnjQ6ear+b6paMdBzw0/A7SEgloEO0c T2JKWeO/dNiamfe+vwKOgWH60S2q8KnizMZoiPCKr65yQhWXPBjhxoD0uKkXJPVg5RLs Uc9E4CBlou6aoJXHAa7mJv8fG+C3rFbdV3M8M16EUl7q8YFcbu1TjoKvoI+jDEZwwRBT JbUljN+8Ozv/pOQ3gSUy4ZitduECRNOokCeogI7tuJBi1CMvSdtXosn8NLkzHpNOI+Ws 40VQ== X-Gm-Message-State: ACrzQf0IT0jMQpgFCsrCql+10JouNsfEQPiLFN64vX4gnECUvw628c5e 17DzCZBeXcHaoGIniKaFNHJKblUSzMg= X-Google-Smtp-Source: AMsMyM6qIPXhnfM4Wlo8TSxbl8OdAYfgsb0Z1lFmKQaxPi9hvgepmJ55/2Kq3XxIeJq3oxJPXXxG8Q== X-Received: by 2002:a05:600c:1d02:b0:3c3:e6f0:6e4b with SMTP id l2-20020a05600c1d0200b003c3e6f06e4bmr12484821wms.202.1666349142706; Fri, 21 Oct 2022 03:45:42 -0700 (PDT) Received: from [127.0.0.1] (92.40.196.37.threembb.co.uk. [92.40.196.37]) by smtp.gmail.com with ESMTPSA id d9-20020a5d6dc9000000b002364c77bc96sm2708769wrz.33.2022.10.21.03.45.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 21 Oct 2022 03:45:41 -0700 (PDT) Date: Fri, 21 Oct 2022 11:45:39 +0100 To: internals@lists.php.net User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: <42A5DAC6-253E-478D-808C-36690FA88315@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Microseconds to error log From: rowan.collins@gmail.com (Rowan Tommins) On 21 October 2022 08:47:30 BST, Mikhail Galanin via internals wrote: >Basically, we have quite a high-loaded environment and we really want >to see timestamps containing milli-/microseconds in our logs=2E I'm not knowledgeable enough to comment on the implementation details, but= from a user point of view I agree the feature would be useful=2E It would = definitely need to be behind an ini setting, though, to avoid existing log = parsers failing unexpectedly on the new format=2E Regards, Hi Mikhail, --=20 Rowan Tommins [IMSoP]