Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 454DB200BCA for ; Mon, 21 Nov 2016 14:58:19 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 427A8160AF9; Mon, 21 Nov 2016 13:58:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 681C5160AEC for ; Mon, 21 Nov 2016 14:58:18 +0100 (CET) Received: (qmail 31652 invoked by uid 500); 21 Nov 2016 13:58:17 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 31642 invoked by uid 99); 21 Nov 2016 13:58:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2016 13:58:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 0C0BEC667D for ; Mon, 21 Nov 2016 13:58:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 8lnIK825bxke for ; Mon, 21 Nov 2016 13:58:15 +0000 (UTC) Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id CC34560E20 for ; Mon, 21 Nov 2016 13:58:14 +0000 (UTC) Received: by mail-wm0-f49.google.com with SMTP id f82so146492688wmf.1 for ; Mon, 21 Nov 2016 05:58:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=jSbyQzrAJ7MRFjOYR/fFecDsS6d2m5/Tt5MYyxeTNe4=; b=kPzCiGWPTGjpirKDyvW+E22s6JE5syz8phT7z3wgk/k1DHuQu97upQRu5FyrfmRfmu pkR+Aj07lKdtckKqLu4oVZO/a5Eey1bj7LW7SJqvww70aKGGf2S89Av6txwO9Qs34bzw 49yfeBkxTYTQ58qyd8rAAaVKP8Pp/9ClL81thLwTgkD58+BwyvuVhgWHuj9M0WcvjwNT fVJZeuG9pWWPOOIKU0asrXREPsOizc7aBiab26FphgBEEl2eG5uhP7UEDxO0DzKE6HkJ BIIxFlEptsI38VZocGyBs8NYrnsEWumurcIn4S33OPrrihJ69JX7xz0MU67GHe8s/F0E C19Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=jSbyQzrAJ7MRFjOYR/fFecDsS6d2m5/Tt5MYyxeTNe4=; b=Qy+0MNpyExHTjd1srliufQYQqNy1ll0jlbNUn1reTtjdXkHlyqPbkIBBwnDuGfPtgi NKjn8Po/GhRwLQuDcm0QDFaqmpGz9i7jkiUxxDZfvMBlFVLR18jSCgYN86A6OE19cI/p ZHh4n2ofm68h+T+6BtdLswkkahZEamLFyBkD+0eIWCoYM04Z9L2Q9ChQZdJpDLm8QtFv /3/G1jTPR0fn2XeCOyDHOzdsKrPIhXsWGeRYusiU7lxvEvPiXL72iYPBdS9r/xo/md4r QOBYo6DZrz4rDwDJleJ1Lku4Nsu8t60jCULnZ4JJWZLwFpODPkKYjKMzdvbE5JIAmB1X X/HA== X-Gm-Message-State: AKaTC03Lzhe2w8yig33XwkPc0pnmrQToVDxilkjXQ2863TPspRgtDg/0g5pBXH56Kzqy2ubjGW+4DOZa16g4Bg== X-Received: by 10.28.47.15 with SMTP id v15mr16065100wmv.76.1479736694183; Mon, 21 Nov 2016 05:58:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.10.85 with HTTP; Mon, 21 Nov 2016 05:58:13 -0800 (PST) In-Reply-To: References: From: Mateusz Zajakala Date: Mon, 21 Nov 2016 14:58:13 +0100 Message-ID: Subject: Re: detailed transaction time logs To: users@trafficserver.apache.org Content-Type: multipart/alternative; boundary=001a11423f58049ad70541d00c89 archived-at: Mon, 21 Nov 2016 13:58:19 -0000 --001a11423f58049ad70541d00c89 Content-Type: text/plain; charset=UTF-8 Sudheer, this is exactly what I was looking for. Many thanks! Mateusz On Mon, Nov 21, 2016 at 2:39 PM, Sudheer Vinukonda < sudheervinukonda@yahoo.com> wrote: > You may try turning on slow logs that record more detailed individual > milestones (time taken for each internal state during the transaction > lifecycle) for transactions that take longer than a specified duration. > > https://docs.trafficserver.apache.org/en/latest/admin- > guide/files/records.config.en.html#proxy-config-http-slow-log-threshold > > - Sudheer > > On Nov 21, 2016, at 3:19 AM, Mateusz Zajakala wrote: > > Hi, > > I'm trying to debug a reverse proxy which occasionally takes longer than > usual time to serve a client. I can see in the logs e.g. that the request > took 10 times the usual amount of time for similar file, however I can't > say whether it was caused by the origin side or client side (i.e. was the > issue when retrieving content from origin or serving it to client). > > Is there any way to get more detailed logs for response time? I'm looking > at 'ttms' value, is there any log to indicate "origin connection time", > "time between sending request to origin and finishing reading response", > "time between starting and finishing serving response to client" etc. That > would help with optimizing... > > If there is nothing in the logs, maybe there is some useful statistic I > should look into? > > Thanks > Mateusz > > --001a11423f58049ad70541d00c89 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sudheer,

this is exactly what I was= looking for. Many thanks!

Mateusz

On Mon, Nov 21, 2016 at 2:39 PM, Su= dheer Vinukonda <sudheervinukonda@yahoo.com> wrote:=
You ma= y try turning on slow logs that record more detailed individual milestones = (time taken for each internal state during the transaction lifecycle) for t= ransactions that take longer than a specified duration.


- Sudheer

On No= v 21, 2016, at 3:19 AM, Mateusz Zajakala <zajakala@gmail.com> wrote:

Hi,<= br>
I'm trying to debug a reverse proxy which occasionally tak= es longer than usual time to serve a client. I can see in the logs e.g. tha= t the request took 10 times the usual amount of time for similar file, howe= ver I can't say whether it was caused by the origin side or client side= (i.e. was the issue when retrieving content from origin or serving it to c= lient).

Is there any way to get more detailed logs for respons= e time? I'm looking at 'ttms' value, is there any log to indica= te "origin connection time", "time between sending request t= o origin and finishing reading response", "time between starting = and finishing serving response to client" etc. That would help with op= timizing...

If there is nothing in the logs, maybe there is so= me useful statistic I should look into?

Thanks
Mateu= sz

--001a11423f58049ad70541d00c89--