trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leif Hedstrom <zw...@apache.org>
Subject Re: FW: How to check storage in traffic server.
Date Fri, 23 Dec 2011 03:25:06 GMT
On 12/22/2011 09:17 AM, James Chris Beaver wrote:
>
> Was the below a silly question or is there a way to better view 
> storage in ATS?
>

You should be able to see it via normal stats, see the below from the 
"cache inspector" stats (but you can query these via Perl API, 
traffic_line -r, or the mgmt APIs in C).

Obviously, if you have more than one volume, you change the "stat" name 
to _1, _2 etc.

-- leif

proxy.process.cache.volume_0.bytes_used=111651840
proxy.process.cache.volume_0.bytes_total=1005346816
proxy.process.cache.volume_0.ram_cache.bytes_used=49377280
proxy.process.cache.volume_0.ram_cache.hits=20666
proxy.process.cache.volume_0.ram_cache.misses=3093
proxy.process.cache.volume_0.pread_count=0
proxy.process.cache.volume_0.percent_full=0
proxy.process.cache.volume_0.lookup.active=0
proxy.process.cache.volume_0.lookup.success=0
proxy.process.cache.volume_0.lookup.failure=0
proxy.process.cache.volume_0.read.active=0
proxy.process.cache.volume_0.read.success=17600
proxy.process.cache.volume_0.read.failure=131577
proxy.process.cache.volume_0.write.active=0
proxy.process.cache.volume_0.write.success=11497
proxy.process.cache.volume_0.write.failure=1042
proxy.process.cache.volume_0.write.backlog.failure=0
proxy.process.cache.volume_0.update.active=0
proxy.process.cache.volume_0.update.success=2353
proxy.process.cache.volume_0.update.failure=1
proxy.process.cache.volume_0.remove.active=0
proxy.process.cache.volume_0.remove.success=0
proxy.process.cache.volume_0.remove.failure=0
proxy.process.cache.volume_0.evacuate.active=0
proxy.process.cache.volume_0.evacuate.success=0
proxy.process.cache.volume_0.evacuate.failure=0
proxy.process.cache.volume_0.scan.active=0
proxy.process.cache.volume_0.scan.success=0
proxy.process.cache.volume_0.scan.failure=0
proxy.process.cache.volume_0.direntries.total=125512
proxy.process.cache.volume_0.direntries.used=11009
proxy.process.cache.volume_0.directory_collision=0
proxy.process.cache.volume_0.frags_per_doc.1=13352
proxy.process.cache.volume_0.frags_per_doc.2=0
proxy.process.cache.volume_0.frags_per_doc.3+=3
proxy.process.cache.volume_0.read_busy.success=3646
proxy.process.cache.volume_0.read_busy.failure=1019
proxy.process.cache.volume_0.write_bytes_stat=0
proxy.process.cache.volume_0.vector_marshals=0
proxy.process.cache.volume_0.hdr_marshals=0
proxy.process.cache.volume_0.hdr_marshal_bytes=0
proxy.process.cache.volume_0.gc_bytes_evacuated=0
proxy.process.cache.volume_0.gc_frags_evacuated=0




Mime
View raw message