[
https://issues.apache.org/jira/browse/TS-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudheer Vinukonda resolved TS-3586.
-----------------------------------
Resolution: Fixed
Unfortunately, there was no consensus on how exactly to report the timing info
during 3xx follow. For the time being, I just added a count of number of
redirects to the slow log to indicate whether or not a txn included redirect
follow. Closing this for now - will open a new jira to track more timing info
for 3xx follow, when/if required.
> 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
> Fix For: 6.0.0
>
>
> 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)
