Download Size Stats


#1

Does Chef server store any stats showing how much data each client is
downloading from the server on a daily basis?

-J


#2

If you reverse http proxy your chef server back end you should be expose
this instrumentation from that layer (nginx, apache, haproxy, …)

I am not currently aware of a Merb (or Rails) plugin to do this
automatically in standalone deployments.

–AJ
On Sep 18, 2012 9:01 AM, “Jason J. W. Williams” jasonjwwilliams@gmail.com
wrote:

Does Chef server store any stats showing how much data each client is
downloading from the server on a daily basis?

-J


#3

On 2012-09-17 18:06, AJ Christensen wrote:

If you reverse http proxy your chef server back end you should be expose
this instrumentation from that layer (nginx, apache, haproxy, …)

I am not currently aware of a Merb (or Rails) plugin to do this
automatically in standalone deployments.

–AJ
On Sep 18, 2012 9:01 AM, “Jason J. W. Williams”
<jasonjwwilliams@gmail.com [1]> wrote:

Does Chef server store any stats showing how much data each client is
downloading from the server on a daily basis?

-J

It mostly depends on how many searches you do. We use searches extensively,
and after 23 days and ~150 chef-clients:

INBOUND 21,691.91MB

OUTBOUND 2,337,301.19MB

so that’s ~700MB per client per day.


Julien Vehent - http://jve.linuxwall.info


#4

On Monday, September 17, 2012 at 3:15 PM, Julien Vehent wrote:

On 2012-09-17 18:06, AJ Christensen wrote:

If you reverse http proxy your chef server back end you should be expose
this instrumentation from that layer (nginx, apache, haproxy, …)

I am not currently aware of a Merb (or Rails) plugin to do this
automatically in standalone deployments.

–AJ
On Sep 18, 2012 9:01 AM, “Jason J. W. Williams”
<jasonjwwilliams@gmail.com (mailto:jasonjwwilliams@gmail.com) [1]> wrote:

Does Chef server store any stats showing how much data each client is
downloading from the server on a daily basis?

-J

It mostly depends on how many searches you do. We use searches extensively,
and after 23 days and ~150 chef-clients:

INBOUND 21,691.91MB

OUTBOUND 2,337,301.19MB

so that’s ~700MB per client per day.


Julien Vehent - http://jve.linuxwall.info

If you’re concerned about the data size and you’re using a reverse proxy, you can turn gzip on at the proxy, as long as you’re using a relatively recent version of Chef (0.10.8+).


Daniel DeLeo


#5

We haven’t had any issues until recently the transfer shot up and we’re
trying to figure out why. No big changes in cookbooks or nodes, and all big
files are HTTP’d off a different mirror server.

-J

On Mon, Sep 17, 2012 at 3:25 PM, Daniel DeLeo dan@kallistec.com wrote:

On Monday, September 17, 2012 at 3:15 PM, Julien Vehent wrote:

On 2012-09-17 18:06, AJ Christensen wrote:

If you reverse http proxy your chef server back end you should be expose
this instrumentation from that layer (nginx, apache, haproxy, …)

I am not currently aware of a Merb (or Rails) plugin to do this
automatically in standalone deployments.

–AJ
On Sep 18, 2012 9:01 AM, “Jason J. W. Williams”
<jasonjwwilliams@gmail.com [1]> wrote:

Does Chef server store any stats showing how much data each client is
downloading from the server on a daily basis?

-J

It mostly depends on how many searches you do. We use searches extensively,
and after 23 days and ~150 chef-clients:

INBOUND 21,691.91MB

OUTBOUND 2,337,301.19MB

so that’s ~700MB per client per day.


Julien Vehent - http://jve.linuxwall.info

If you’re concerned about the data size and you’re using a reverse proxy,
you can turn gzip on at the proxy, as long as you’re using a relatively
recent version of Chef (0.10.8+).


Daniel DeLeo