[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2015-03-16 Thread jacksontj
Github user jacksontj commented on the pull request: https://github.com/apache/trafficserver/pull/104#issuecomment-82027946 @zwoop --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this featur

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2015-03-09 Thread jacksontj
Github user jacksontj commented on the pull request: https://github.com/apache/trafficserver/pull/104#issuecomment-77976157 That would make sense too, I'm just going off the docs: ``` with a ``chm`` value of +``-`` the medium was disk cache. ``` Seems o

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2015-03-09 Thread zwoop
Github user zwoop commented on the pull request: https://github.com/apache/trafficserver/pull/104#issuecomment-77975742 Hmmm that feels like it'd be a different log tag, no? The intent with this field is to show which cache level we are serving out of, e.g RAM vs rotational disk vs SS

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2015-03-09 Thread jacksontj
Github user jacksontj commented on the pull request: https://github.com/apache/trafficserver/pull/104#issuecomment-77974860 Is it possible to log the volume that served the cache response? Right now it seems that you log "-" when it hits disk, but it would be nice if we could know whi

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2015-03-09 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/trafficserver/pull/104 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2014-09-10 Thread jpeach
Github user jpeach commented on the pull request: https://github.com/apache/trafficserver/pull/104#issuecomment-55179815 Ok, I was confused by the parallel discussion in the Jira ticket. What sayeth thou @SolidWallOfCode? --- If your project is set up for it, you can reply to this em

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2014-09-10 Thread zwoop
Github user zwoop commented on the pull request: https://github.com/apache/trafficserver/pull/104#issuecomment-55179626 Yeah, I did. My gut reaction is that we ought to have amc chime in on this, to make sure this aligns with future directions re: cache hierarchies. --- If your proje

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2014-09-10 Thread jpeach
Github user jpeach commented on the pull request: https://github.com/apache/trafficserver/pull/104#issuecomment-55179361 @zwoop, can you take a look at this and merge if you think it is OK? --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2014-08-22 Thread RyanFrantz
Github user RyanFrantz commented on the pull request: https://github.com/apache/trafficserver/pull/104#issuecomment-53124539 Per https://issues.apache.org/jira/browse/TS-3036 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well

[GitHub] trafficserver pull request: TS-3036: Added the 'chm' logging field

2014-08-22 Thread RyanFrantz
GitHub user RyanFrantz opened a pull request: https://github.com/apache/trafficserver/pull/104 TS-3036: Added the 'chm' logging field The 'chm' logging field notes, in the case of a cache hit, if the medium the hit was served from was RAM. You can merge this pull request into a Git