Forge Home

spm_monitor

pdk
Install and configure Sematext Infra & App Agent

8,680 downloads

4,115 latest version

5.0 quality score

Version information

  • 1.0.2 (latest)
  • 1.0.1
  • 1.0.0
  • 0.8.0
released Jan 29th 2019
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
  • Puppet >= 4.10.0 < 7.0.0
  • CentOS
    ,
    RedHat
    ,
    Debian
    ,
    Ubuntu

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'sematext-spm_monitor', '1.0.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add sematext-spm_monitor
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install sematext-spm_monitor --version 1.0.2

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

sematext/spm_monitor — version 1.0.2 Jan 29th 2019

spm_monitor

Table of Contents

  1. Description
  2. Setup
  3. Usage
  4. Limitations
  5. Contributions

Description

The spm_monitor module can install and configure Sematext Infra & App agents on CentOS, RedHat, Debian and Ubuntu systems.

Install

Install spm_monitor as a module in your Puppet master's module path.

puppet module install sematext-spm_monitor

Usage

Using the spm_monitor::install Class

To install Sematext Infra & App agents, just declare the spm_monitor::install class.

include 'spm_monitor::install'

or

class { 'spm_monitor::install':}

Using the spm_monitor::configure Class

To configure Sematext Infra & App agents, you need to declare the spm_monitor::configure class with the correct parameters for the application type.

class { 'spm_monitor::configure':
  'monitoring_token' => 'MONITORING_TOKEN',
  'infra_token'      => 'INFRA_TOKEN',
  'agent_type'       => 'standalone'
  'app_type'         => 'mysql',
  'agent_args'       => {
    'SPM_MONITOR_MYSQL_DB_USER'     => 'mysql-user',
    'SPM_MONITOR_MYSQL_DB_PASSWORD' => 'mysql-password',
  }
}

class { 'spm_monitor::configure':
  'monitoring_token' => 'MONITORING_TOKEN',
  'infra_token'      => 'INFRA_TOKEN',
  'agent_type'       => 'standalone'
  'app_type'         => 'elasticsearch',
  'agent_args'       => {
    'SPM_MONITOR_ES_NODE_HOSTPORT' => 'localhost:9200',
  }
}

class { 'spm_monitor::configure':
  'monitoring_token' => 'MONITORING_TOKEN',
  'infra_token'      => 'INFRA_TOKEN',
  'agent_type'       => 'standalone'
  'app_type'         => 'zookeeper',
  'agent_args'       => {
    'jmx_host' => 'localhost',
    'jmx_port' => '3000',
  }
}

class { 'spm_monitor::configure':
  'monitoring_token' => 'MONITORING_TOKEN',
  'infra_token'      => 'INFRA_TOKEN',
  'agent_type'       => 'standalone'
  'app_type'         => 'kafka',
  'app_subtype'      => 'kafka-broker',
  'agent_args' => {
    'jmx_host' => 'localhost',
    'jmx_port' => '3000',
  }
}

Limitations

This module is tested and officially supported on CentOS/RedHat 6 and 7, Debian 8 and 9 and Ubuntu 16.04 and 18.04. Testing on other platforms has been light and cannot be guaranteed.

Contributions

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request