The power of leveraging Ansible Tower against Dynatrace problem detection first dawned on me after reading a post from the excellent Wolfgang Beer. He talks about the solution in the abstract and gives a pretty concise guide on how to leverage APM to use event driven metrics to launch a Playbook, but I ran in to issues almost instantly. The problem isn’t obvious straight away, most people run Dynatrace as . . .
Ansible Tower and Netbox are two of the greatest tools in the DevOps toolchain, and the integration is seemingly painless on the surface (and really it isn’t all that bad) but there is a little nuance to it. Both application stacks provide a RESTful API so sending data between the two should be as simple as firing some JSON between them right? Even with Ansible being a YAML focused platform . . .
Anyone that’s ever spoken to me about tech for more than 30 seconds will know how much I love Ansible and even more Ansible Tower (Red Hat’s REST API and Web Services console) and with good cause; it’s top of class Infrastructure Automation and easily more flexible, scalable and and lightweight than Cloud Formation, Chef, Puppet, Salt or any of it’s contemporaries. On top of that, it’s documentation is second . . .