Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status

RSS

signalfx (2) Versions 0.1.0

Installs/Configures signalfx metricproxy

Policyfile
Berkshelf
Knife
cookbook 'signalfx', '= 0.1.0', :supermarket
cookbook 'signalfx', '= 0.1.0'
knife supermarket install signalfx
knife supermarket download signalfx
README
Dependencies
Changelog
Quality 0%

chef-signalfx

Chef cookbook for mangaging the SignalFX metricproxy.

Requirements

cookbooks

  • golang ~> 1.4
  • git

Attributes

signalfx::default

<table>
<tr>
<th>Key</th>
<th>Type</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td><tt>[:signalfx][:directory]</tt></td>
<td>String</td>
<td>Home directory for the proxy. The metricproxy binary will be linked here.</td>
<td><tt>/opt/signalfx</tt></td>
</tr>
<tr>
<td><tt>[:signalfx][:user]</tt></td>
<td>String</td>
<td>User to run as. Will be created if it does not exist.</td>
<td><tt>signalfx</tt></td>
</tr>
<tr>
<td><tt>[:signalfx][:repo]</tt></td>
<td>String</td>
<td>Location of the metricproxy repo.</td>
<td><tt>github.com/signalfx/metricproxy</tt></td>
</tr>
<tr>
<td><tt>[:signalfx][:config_file]</tt></td>
<td>String</td>
<td>Path to the configuration file.</td>
<td><tt>/etc/sfdbconfig.conf</tt></td>
</tr>
<tr>
<td><tt>[:signalfx][:log_dir]</tt></td>
<td>String</td>
<td>Directory to log to.</td>
<td><tt>/var/log/sfproxy</tt></td>
</tr>
<tr>
<td><tt>[:signalfx][:pid_file]</tt></td>
<td>String</td>
<td>File to write the PID to.</td>
<td><tt>/var/run/metricproxy.pid</tt></td>
</tr>
<tr>
<td><tt>[:signalfx][:config][:stats_delay]</tt></td>
<td>String</td>
<td>/td>
<td><tt>1s</tt></td>
</tr>
<tr>
<td><tt>[:signalfx][:config][:forward]</tt></td>
<td>Array</td>
<td>Each item is an object containing a configuration to forward incoming metrics.</td>
<td></td>
</tr>
<tr>
<td><tt>[:signalfx][:config][:listen]</tt></td>
<td>Array</td>
<td>Each item is an object containing a configuration to listen for incoming metrics.</td>
<td></td>
</tr>
</table>

Usage

signalfx::default

Just include signalfx in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[signalfx]"
  ]
}

Dependent cookbooks

golang >= 0.0.0
git >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

signalfx CHANGELOG

This file is used to list changes made in each version of the signalfx cookbook.

0.1.0

  • [hexedpackets] - Initial release of signalfx

Foodcritic Metric
            

0.1.0 failed this metric

FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:3
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:4
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:5
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:6
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:7
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:8
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:10
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:11
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/attributes/default.rb:30
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:7
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:9
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:12
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:15
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:19
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:20
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:23
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:24
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:28
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:30
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:31
FC001: Use strings in preference to symbols to access node attributes: /tmp/cook/4447677428dcc7bf07343996/signalfx/recipes/default.rb:37