Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 1. Event-Driven Ansible controller overview
Event-Driven Ansible is a highly scalable, flexible automation capability that works with event sources such as other software vendors' monitoring tools. These tools monitor IT solutions and identify events and automatically implement the documented changes or response in a rulebook to handle that event.
The following procedures form the user configuration:
- Credentials
- Credential types
- Projects
- Decision environments
- Red Hat Ansible Automation Platform credential
- Rulebook activations
- Rulebook activations troubleshooting
- Rule audit
- Simplified event routing
- Performance tuning for Event-Driven Ansible controller
- Event filter plugins
- Event-Driven Ansible logging strategy
- API documentation for Event-Driven Ansible controller is available at https://<gateway-host>/api/eda/v1/docs
- To meet high availability demands, Event-Driven Ansible controller shares centralized Redis (REmote DIctionary Server) with the Ansible Automation Platform UI. When Redis is unavailable, you will not be able to create or sync projects, or enable rulebook activations.
In new installations of Ansible Automation Platform 2.6, using Event-Driven Ansible controller’s API to manage organizations, teams, or users requires an automated sync of up to 15 minutes to propagate changes to the rest of the Ansible Automation Platform components. To avoid potential errors and ensure immediate access, use the platform gateway API instead, or the unified UI.