Hi Adan, I answered inline based on my understand of astats, if I am wrong, hopefully someone will correct me. Thanks, Dave
On Tue, Jan 24, 2017 at 1:40 AM, Adan Alper <[email protected]> wrote: > Hello, > > > > First of all thanks for the previous replies they were very helpful. > > > > We currently have a running cache that knows how to read remap rules from > traffic ops, acquire, deliver and export a stats file (currently with dummy > values) to traffic monitor. > > My question is regarding some of the astat counters definitions. > > What is the definition of the following counters: > > 1. plugin.remap_stats.delivery-service-fqdn.in_bytes – What is the > definition of in_bytes? Bytes from client or from origin server? > -- in_bytes are bytes received by the server. This can be from a client (request) or an org server (content). > 2. plugin.remap_stats.delivery-service-fqdn.out_bytes – What is the > definition of out_bytes? Bytes sent to client? > -- out_bytes are bytes sent by the server, this can be to a client (content) or org (request) > > 3. plugin.remap_stats.delivery-service-fqdn.statusXXX – Does this > count the status sent to client or received by origin server? > -- This is the status sent to the client. I believe if a cache receives a 5xx from an upstream server, like an origin, it will pass it along and this counter will be updated, but I could be wrong. > > 4. configReloadRequests, lastReloadRequest, configReloads – Do these > counters count ATS reloads or configuration updates? Are these counters > important for traffic monitor or just for debug? > -- I am not sure about this one. If I was to guess I would guess it was for ATS config reloads. This is not used by TM afaik. > 5. astatsLoad – Time astats file was last updated? > -- again, not sure, but I would guess it is the timestamp that the astats plugin was last loaded. > > > Thanks, > > > > Adan >
