Ansible

Note: This document contains references to the Ansible® documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

The Splunk AppDynamics Ansible Collection installs and configures Splunk AppDynamics agents. You can automatically download all the supported agents from the Ansible Galaxy to the Ansible® control node. If you are using the on-prem version, download the agents from the local repository. This makes it easy to retrieve and upgrade agents.

For a description of available deployment options, see Common Role Variables.

The Splunk AppDynamics Ansible Collection is built to support (immutable) infrastructure as code deployment, where agents are upgraded with basic configuration. Hence, the collection does not consider any manual configuration changes on the target servers.

Warning: Custom agent configurations are supported only if these configurations are written to an Ansible role. The Splunk AppDynamics Ansible Collection will overwrite any local or pre-existing configuration with the variables that are defined in the playbook. Therefore, we strongly recommend that you convert any custom agent configuration into an Ansible role to ensure consistency of deployments and configurations across your estate.

The following diagram explains the workflow:


Download Splunk AppDynamics Agents from the Download portal or custom endpoint.

Download the Splunk AppDynamics Ansible Collection from galaxy.ansible.com.

(Optional) Download the agent binaries from the custom endpoint if maintaining a file server.

Configure the agents using playbook. See Playbooks.

The Control Node, which comprises of file server and playbooks, pushes the configuration to the managed nodes.