# bprobe_cookbook

**Repository Path**: mirrors_boundary/bprobe_cookbook

## Basic Information

- **Project Name**: bprobe_cookbook
- **Description**: The Boundary bprobe cookbook.
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-11-23
- **Last Updated**: 2026-01-04

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

## DEPRECATED - Unsupported

New boundary meter cookbook is here https://github.com/boundary/boundary-meter_cookbook

### The bprobe Cookbook

This cookbook has two functions, the first is to install the Boundary bprobe daemon on your machine. The second is to interface with the Boundary API providing bprobe with certificates, adding the meter to your account and adding the meter to a group. The latter is provided by two LWRP's bprobe and bprobe_certificates. Examples of their usage can be found in the default recipe. This recipe can be used as is to install bprobe and configure it using the Boundary API. To get things running adjust the attributes in api.rb to match your Boundary account, upload the cookbooks in this repo and apply bprobe::default to a system.

#### Dependencies

Dependencies and their requisite versions, when necessary, are specified in metadata.rb.

#### Configuration Options

##### API Keys

Setup your API keys in attributes/api.rb

```ruby
default[:boundary][:api][:hostname] = "api.boundary.com"
default[:boundary][:api][:org_id] = "dlekd93DGJDJw9diekd98"
default[:boundary][:api][:key] = "PI1ldnfKENFMslekd29dl"
```

##### Host Tags

The easiest way to set host tags is to use override_attributes in your server roles

```ruby
name "db-server"
description "Installs Boundary bprobe and sets some meter tags"
recipes "mysql","bprobe::default"

override_attributes({
  :boundary => {
    :bprobe => {
      :tags => [ "linux", "ubuntu", "database-server" ]
    }
  }
})
```ruby

##### Interfaces

By default, bprobe listens on all interfaces. However, you can manually specify the interfaces you wish to monitor.

```ruby
override_attributes({
  :boundary       => {
    :bprobe       => {
      :interfaces => [ "eth0", "eth2" ]
    }
  }
})
```

##### Hostname

By default Boundary will use `node[:fqdn]` as the hostname. You can override this by setting a `[:boundary][:hostname]` attribute with a higher precedence then default.

#### EC2

This cookbook includes automatic detection and tagging of your meter with various EC2 attributes such as security group and instance type.

#### OpsWorks

If you are using OpsWorks this cookbook should work out of the box (with the above dependencies). This cookbook also includes automatic detection and tagging of your meter with layers, stack name and applications if any exist.