0

In July, we released Ansible Tower 3. In this blog series, we will take a deeper dive into Tower changes that were all designed to make our product simpler and easier to scale Ansible automation across your environments. In our last post, Jared Tabor, Ansible Tower Software Engineer, highlights what's new in the Tower 3 user interface.
If you’d like to learn more about the release, our Director of Product Bill Nottingham for wrote a complete overview of the Ansible Tower 3 updates.
Introducing Tower Notifications
One of the exciting new features of Ansible Tower 3 is notifications. Tower notifications provide a mechanism of signaling when Tower jobs succeed or fail. This can take the form of sending a message to a Slack channel or sending an HTTP POST to another service to trigger other actions.
In Tower 3 we support the following notification types:
- Email
- Slack
- Hipchat
- Pagerduty
- Twilio
- IRC
- Webhook (POST)
Concepts
There are two important concepts to understand when it comes to notifications in Tower.
1. Notification Templates
These define the properties of where a notification will be sent and who will get notified. If you are using the Slack notification type, then this will include the token and Continue reading