Ansible Role: al-agents

This playbook helps install and set up the Alert Logic agent.

Requirements

Here are the supported systems:

Debian versions:

• squeeze
• wheezy
• jessie

Ubuntu versions:

• 10.x
• 12.x
• 14.x
• 16.x
• 18.x

RHEL/CentOS versions:

• 6.x
• 7.x

SuSE versions:

• 12.1
• 12.0
• 11.4
• 11.3

Amazon Linux versions:

• Karoo

Windows versions:

• Windows Server 2003+SP1, 2008, 2012, 2016
• Windows XP+SP1, Vista, 7, 8, 10

Role Variables

• al_agent_registration_key - Your unique registration key. This is required unless using supported cloud services (AWS, Azure). Default is your_registration_key_here.
• al_agent_for_imaging - This variable indicates if the agent will be set up and ready to use. If set to true, the agent will be installed but not started, allowing for snapshots to be taken. If set to false, the agent is installed and started right away. Default is false.
• al_agent_egress_host, al_agent_egress_port - Normally, all traffic goes to https://vaporator.alertlogic.com. Use these variables if you have a machine handling outbound traffic (like a NAT box). If you set your URL, make sure it's correctly formatted. Default is https://vaporator.alertlogic.com.
• al_agent_proxy_url - By default, the al-agent doesn’t need a proxy. If you want to use one, both al_agent_egress_host and al_agent_proxy_url must be set. Ensure the proxy URL is correctly formatted. Default is nil.

Dependencies

• No known dependencies.

Example Playbook

---
- name: Apply AL Agent installation to specific hosts
  hosts: al_agents
  roles:
    - { role: alertlogic.al_agents}

Configurations

The variable al_agent_for_imaging determines how you install the agent. It is a boolean (true/false) and defaults to false. If you set it to true, the agent will be prepared for imaging only and won't be fully set up.

Using the default settings to install the agent will set it up and start it right away. If your registration key is entered correctly, you should see your host in the Alert Logic Console in about 15 minutes. Note: In AWS and Azure, the key is optional and usually not needed.

Contributing

1. Fork the GitHub repository.
2. Create a new feature branch (like add_component_x).
3. Make your changes.
4. Write tests for your changes (if needed).
5. Run the tests to ensure everything passes.
6. Submit a Pull Request on GitHub.

License and Authors

License:

This is distributed under the Apache 2.0 license.

Authors: Muram Mohamed (mmohamed@alertlogic.com)
Justin Early (jearly@alertlogic.com)