Alert Logic remote collector

This playbook is used to install and configure the Alert Logic remote collector service.

Requirements

Debian and Enterprise Linux are the tested and supported platforms.

Role Variables

• al_remote_registration_key - your unique registration key, required except in supported cloud deployments (AWS, Azure) String defaults to your_registration_key_here

Dependencies

• no known dependencies

Example Playbook

---
- name: Install Alert Logic remote collector to specific hosts
  hosts: al_collectors
  roles:
    - role: deekayen.alremote
      vars:
        al_remote_registration_key: 'useWhenNotInAWSorAzure'

Configurations

The variable al_remote_for_imaging determine your installation type. It is a boolean value and by default is false. Setting this value to true will prepare your agent for imaging only and will not provision the agent.

Performing an agent install using the cookbook's default attributes, will setup the agent and provision the instance immediately. If you have properly set your registration key, your host should appear within Alert Logic's Console within 15 minutes. Note: in AWS and Azure deployments the use of the key is optional and in general not necessary.

License and Authors

Distributed under the Apache 2.0 license.

Original Authors of Alert Logic agent role: Muram Mohamed (mmohamed@alertlogic.com) Justin Early (jearly@alertlogic.com)

Derivative work remote collector install by: David Norman deekayen