[jira] [Updated] (TS-3646) "chm" log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3646: -- Component/s: (was: Docs) Documentation > "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: Documentation >Affects Versions: 5.3.0 >Reporter: Stephane Bagneris >Assignee: Jon Sime > Fix For: Docs > > > 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)
[jira] [Updated] (TS-3646) "chm" log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3646: -- Component/s: (was: Logging) Docs > "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: Docs >Affects Versions: 5.3.0 >Reporter: Stephane Bagneris >Assignee: Jon Sime > Fix For: Docs > > > 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)
[jira] [Updated] (TS-3646) "chm" log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3646: Assignee: Jon Sime > "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 >Assignee: Jon Sime > Fix For: Docs > > > 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)
[jira] [Updated] (TS-3646) "chm" log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3646: -- Fix Version/s: (was: 6.0.0) Docs > "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: Docs > > > 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)
[jira] [Updated] (TS-3646) "chm" log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3646: --- Issue Type: Improvement (was: Bug) > "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)
[jira] [Updated] (TS-3646) "chm" log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3646: --- Component/s: Logging > "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: Bug > 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)
[jira] [Updated] (TS-3646) "chm" log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3646: --- Affects Version/s: 5.3.0 > "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: Bug > 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)
[jira] [Updated] (TS-3646) "chm" log field and TCP_MEM_HIT are the same feature
[ https://issues.apache.org/jira/browse/TS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3646: --- Fix Version/s: 6.0.0 > "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: Bug > 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)
