[
https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563952#comment-14563952
]
Leif Hedstrom commented on TS-3646:
-----------------------------------
This is by design actually. Even though there is (sometimes) overlap between
the two, they are not the same. %<chm> will always show the cache hit / miss
status, and the "hierarchy" information (currently RAM and disk only, but has
future extensions possible). %<crc> has a significant overload of information,
which can cause you to lose vital information.
As an example, %<crc> can show a result of "TCP_REFRESH_HIT". However, you can
*not* tell if it was a RAM or a disk cache hit. This is partially why %<chm>
was added.
Maybe we should turn this into a documentation issue, and clarify the
differences better?
> "chm" log field and TCP_MEM_HIT are the same feature
> ----------------------------------------------------
>
> Key: TS-3646
> URL: https://issues.apache.org/jira/browse/TS-3646
> Project: Traffic Server
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 5.3.0
> Reporter: Stephane Bagneris
> Fix For: 6.0.0
>
>
> The documented "chm" log field feature which will differentiate between
> RAM_HIT and DISK_HIT as already been implemented with the addition of
> TCP_MEM_HIT in the "crc" filed. Having both feature is redundant and
> confusing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
