You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2015/05/07 01:09:59 UTC

[jira] [Updated] (TS-3586) milestones/slow log data do not have visibility to internal redirect follow

     [ https://issues.apache.org/jira/browse/TS-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudheer Vinukonda updated TS-3586:
----------------------------------
    Description: 
milestones/slow log data do not have visibility to internal redirect follow. It is still under discussion on how best to fit the data (if at all), and the impact the change would have on the slow log API, log tags, metrics, slow log format etc.

For the time being, added the *redirection_tries* to the slow log to indicate how many internal redirect follow events occurred on the TXN.

  was:milestones/slow log data do not have visibility to internal redirect follow. It is still under discussion on how best to fit the data (if at all), and the impact the change would have on the slow log API, log tags, metrics, slow log format etc.


> milestones/slow log data do not have visibility to internal redirect follow
> ---------------------------------------------------------------------------
>
>                 Key: TS-3586
>                 URL: https://issues.apache.org/jira/browse/TS-3586
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: HTTP
>            Reporter: Sudheer Vinukonda
>
> milestones/slow log data do not have visibility to internal redirect follow. It is still under discussion on how best to fit the data (if at all), and the impact the change would have on the slow log API, log tags, metrics, slow log format etc.
> For the time being, added the *redirection_tries* to the slow log to indicate how many internal redirect follow events occurred on the TXN.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)