You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficserver.apache.org by Kevin Kruzich <kk...@gmail.com> on 2014/09/30 21:21:38 UTC
traffic server usage / stats (clarification)
I'm resending with clarifications: Trying to calculate bandwidth usage from
ATS (GET requests to internet clients). The counters
proxy.process.net.read_bytes and proxy.process.net.write_bytes appear to be
the correct choice but 1) what is difference between net.read, net.write
and 2) Assuming this count is since start of proc, how might I slice up the
data to increments such as day/week/month?
Thank you,
--kkruzich
---------- Forwarded message ----------
From: Kevin Kruzich <kk...@gmail.com>
Date: Mon, Sep 29, 2014 at 7:17 PM
Subject: traffic server usage / stats
To: users@trafficserver.apache.org
Hello --I'm trying to determine how much data has been served via a given
ATS server, specifically GET requests to internet clients. There are many
stats available on the /stats page (same or similar results are offered via
'traffic_line -r'), yet of all of these, the one which seems the closest
I'm looking for is proxy.process.net.read_bytes and .net.write_bytes. But
two questions about this:
1) What is meant by net.read vs. net.write?
2) This is a count since last start of the process. How might I calculate
bytes served in a day/week/month?
http://<ats-server>:8080/stat/ <http://img1.las:8080/stat/>
proxy.process.net.read_bytes=100282348193
proxy.process.net.write_bytes=363453506715
Re: traffic server usage / stats (clarification)
Posted by Kevin Kruzich <kk...@gmail.com>.
Thank you James. I took notice of
proxy.node.http.user_agent_total_request_bytes
and the others you noted but my /stat/ page is showing them as 0. I suppose
I turned to, and continue to be focused on, proxy.process.net.read_bytes
(and net.write) because they have a significant count --a number I would
more likely believe is a count of bytes served.
On Tue, Sep 30, 2014 at 1:51 PM, James Peach <jp...@apache.org> wrote:
>
> On Sep 30, 2014, at 12:21 PM, Kevin Kruzich <kk...@gmail.com> wrote:
>
> >
> > I'm resending with clarifications: Trying to calculate bandwidth usage
> from ATS (GET requests to internet clients). The counters
> proxy.process.net.read_bytes and proxy.process.net.write_bytes appear to be
> the correct choice
>
> I believe that these metrics count all bytes sent and received over the
> network. You might want to measure
>
> proxy.node.http.user_agent_total_request_bytes
> proxy.node.http.user_agent_total_response_bytes
> proxy.node.http.origin_server_total_request_bytes
> proxy.node.http.origin_server_total_response_bytes
>
> > but 1) what is difference between net.read, net.write
>
> "read" is bytes read (received) from the network, "write" is bytes written
> (sent) to the network
>
> > and 2) Assuming this count is since start of proc, how might I slice up
> the data to increments such as day/week/month?
>
> Typically, people sample the metrics into a monitoring system, like
> Graphite or Circonus. Those kinds of systems will aggregate and rate
> convert metrics to give you throughput and utilization numbers.
>
> >
> >
> > Thank you,
> > --kkruzich
> >
> > ---------- Forwarded message ----------
> > From: Kevin Kruzich <kk...@gmail.com>
> > Date: Mon, Sep 29, 2014 at 7:17 PM
> > Subject: traffic server usage / stats
> > To: users@trafficserver.apache.org
> >
> >
> >
> > Hello --I'm trying to determine how much data has been served via a
> given ATS server, specifically GET requests to internet clients. There are
> many stats available on the /stats page (same or similar results are
> offered via 'traffic_line -r'), yet of all of these, the one which seems
> the closest I'm looking for is proxy.process.net.read_bytes and
> .net.write_bytes. But two questions about this:
> >
> > 1) What is meant by net.read vs. net.write?
> > 2) This is a count since last start of the process. How might I
> calculate bytes served in a day/week/month?
> >
> >
> > http://<ats-server>:8080/stat/
> >
> > proxy.process.net.read_bytes=100282348193
> >
> > proxy.process.net.write_bytes=363453506715
> >
> >
>
>
Re: traffic server usage / stats (clarification)
Posted by James Peach <jp...@apache.org>.
On Sep 30, 2014, at 12:21 PM, Kevin Kruzich <kk...@gmail.com> wrote:
>
> I'm resending with clarifications: Trying to calculate bandwidth usage from ATS (GET requests to internet clients). The counters proxy.process.net.read_bytes and proxy.process.net.write_bytes appear to be the correct choice
I believe that these metrics count all bytes sent and received over the network. You might want to measure
proxy.node.http.user_agent_total_request_bytes
proxy.node.http.user_agent_total_response_bytes
proxy.node.http.origin_server_total_request_bytes
proxy.node.http.origin_server_total_response_bytes
> but 1) what is difference between net.read, net.write
"read" is bytes read (received) from the network, "write" is bytes written (sent) to the network
> and 2) Assuming this count is since start of proc, how might I slice up the data to increments such as day/week/month?
Typically, people sample the metrics into a monitoring system, like Graphite or Circonus. Those kinds of systems will aggregate and rate convert metrics to give you throughput and utilization numbers.
>
>
> Thank you,
> --kkruzich
>
> ---------- Forwarded message ----------
> From: Kevin Kruzich <kk...@gmail.com>
> Date: Mon, Sep 29, 2014 at 7:17 PM
> Subject: traffic server usage / stats
> To: users@trafficserver.apache.org
>
>
>
> Hello --I'm trying to determine how much data has been served via a given ATS server, specifically GET requests to internet clients. There are many stats available on the /stats page (same or similar results are offered via 'traffic_line -r'), yet of all of these, the one which seems the closest I'm looking for is proxy.process.net.read_bytes and .net.write_bytes. But two questions about this:
>
> 1) What is meant by net.read vs. net.write?
> 2) This is a count since last start of the process. How might I calculate bytes served in a day/week/month?
>
>
> http://<ats-server>:8080/stat/
>
> proxy.process.net.read_bytes=100282348193
>
> proxy.process.net.write_bytes=363453506715
>
>