How do I Configure Custom Logging Aggregator in Ansible Automation Platform?

Solution Verified - Updated -

Environment

  • Ansible Tower 3.8.x
  • Ansible Automation Platform 2.x
  • Controller 4.x

Issue

  • How do I point Ansible Tower to a custom logging aggregator apart from SPLUNK, LOGSTASH, SUMOLOGIC & LOGGLY.
  • How do I point Controller to a custom logging aggregator apart from SPLUNK, LOGSTASH, SUMOLOGIC & LOGGLY.

Resolution

  • Selecting Other logging aggregator service in Ansible Tower :

    If you want to use any other logging aggregator service apart from SPLUNK, LOGSTASH, SUMOLOGIC & LOGGLY, you can select "LOGGING AGGREGATOR TYPE" as other in the "LOGGING" section.

    Settings -> System -> LOGGING

    For more details on setting up the Logging Aggregator in Ansible Tower, refer the following documentation link:
    Set up logging with tower

  • Selecting Other logging aggregator service in Ansible Automation Platfrom :

    If you want to use any other logging aggregator service apart from SPLUNK, LOGSTASH, SUMOLOGIC & LOGGLY, you can select "LOGGING AGGREGATOR TYPE" as other in the "LOGGING" section.

    Settings -> Logging -> Logging Aggregator Type

    For more details on setting up the Logging Aggregator in AAP2.x, refer the following documentation link:
    Set up logging with AAP

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

1 Comments

Log in to comment
MS Newbie 7 points
6 February 2023 2:19 PM

External loggers e.g. Logstash or Kafka(here as Other) require some additional settings like 'logstash_pipeline_name' for logstash or 'topic' for Kafka. It would be helpful if you added info on how to set them in Tower/AWX/Automation platform.