[jira] [Updated] (TS-3220) Update http cache stats so we can determine if a response was served from ram cache

["Bryan Call (JIRA)" <ji...@apache.org>]

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

Bryan Call updated TS-3220:
---------------------------
    Fix Version/s: 5.3.0

> Update http cache stats so we can determine if a response was served from ram cache
> -----------------------------------------------------------------------------------
>
>                 Key: TS-3220
>                 URL: https://issues.apache.org/jira/browse/TS-3220
>             Project: Traffic Server
>          Issue Type: Improvement
>            Reporter: Bryan Call
>             Fix For: 5.3.0
>
>
> Currently we use a combination of ram cache stats and some http ram cache information to try to determine if the response was served from ram cache.  The ram cache stats don't know about http and the entry in ram cache might not be valid, so it is possible to have a ram cache hit from the cache's point of view, but not serve the response from cache at all.
> The http cache stats are missing a few stats to determine if the response was served from ram.  We would need to add stat form ims response was served from ram {{proxy.process.http.cache_hit_mem_ims}} and a stat if the stale response was served from ram {{proxy.process.http.cache_hit_mem_stale_served}}.
> Ram cache stats for reference
> {code}
> proxy.process.cache.ram_cache.hits
> proxy.process.cache.ram_cache.misses
> {code}
> Current http cache stats for reference
> {code}
> proxy.process.http.cache_hit_fresh
> proxy.process.http.cache_hit_mem_fresh
> proxy.process.http.cache_hit_revalidated
> proxy.process.http.cache_hit_ims
> proxy.process.http.cache_hit_stale_served
> proxy.process.http.cache_miss_cold
> proxy.process.http.cache_miss_changed
> proxy.process.http.cache_miss_client_no_cache
> proxy.process.http.cache_miss_client_not_cacheable
> proxy.process.http.cache_miss_ims
> {code}



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