With our Red Hat Ansible Automation Platform dashboards, you can easily track and visualize your Ansible Automation Platform logs, keep an eye on your jobs, and monitor instance memory.
Built with our infrastructure agent and our Prometheus OpenMetrics integration, the Ansible Automation Platform integration gives you a set of pre-built that let you view your most critical query data, all in one place.
After setting up the integration with New Relic, see your data in like these, right out of the box.
Install the infrastructure agent
The New Relic infrastructure agent is the foundation for getting your Ansible Automation Platform data into New Relic. If you haven't already done so, install the agent using one of these options:
Our guided install is a CLI tool that inspects your system and installs the infrastructure agent alongside the application monitoring agent that best works for your system. To learn more about how our guided install works, check out our Guided install overview.
If you'd rather install our infrastructure agent manually, you can follow a tutorial for manual installation for Linux, Windows, or macOS.
Integrate Red Hat Ansible Automation Platform with New Relic
Once installed, the infrastructure agent can ingest data from your app and send it to New Relic, but you still need to integrate – or establish a line of communication – between the agent and your app. Once integrated, you can get started with an out of the box monitoring solution for your Ansible Automation Platform app.
Once logged into Ansible Automation Platform, navigate to the Users section, select admin and then add a token to the user. Copy the token and save it in your desired path.
Here is an example token:
Create a file named "bearer_token_file" in your desired path.
# Whether the integration should run in verbose mode or not. Defaults to false.
# Whether the integration should run in audit mode or not. Defaults to false.
# Audit mode logs the uncompressed data sent to New Relic. Use this to log all data sent.
# It does not include verbose mode. This can lead to a high log volume, use with care.
# The HTTP client timeout when fetching data from endpoints. Defaults to 30s.
# scrape_timeout: "30s"
# Length in time to distribute the scraping from the endpoints.
# Number of worker threads used for scraping targets.
# For large clusters with many (>400) endpoints, slowly increase until scrape
# time falls between the desired `scrape_duration`.
# Increasing this value too much will result in huge memory consumption if too
# many metrics are being scraped.
# Default: 4
# worker_threads: 4
# Whether the integration should skip TLS verification or not. Defaults to false.
You can use our log forwarding to forward Ansible Automation Platform logs to New Relic.
On Linux machines, your log file named logging.yml should be present in the below path:
If you don't see your log file in the above path, then you will need to create a log file by following the above log forwarding documentation.
To create the log file, add the script below to the logging.yml file:
- name: ansible-tower.log
Before you can start reading your data use the instructions in our infrastructure agent docs to restart your infrastructure agent.
You can use this NRQL query to view your Ansible Automation Platform data:
FROM Metric SELECT latest(awx_pending_jobs_total) AS 'Pending Jobs', latest(awx_running_jobs_total) AS 'Running Jobs'
See Ansible Automation Controller metrics in a dashboard
With the infrastructure agent installed and instrumented with your app, you can view your raw data in our Metrics & events. Our default transform that raw data into charts and graphs, which provide a bird's eye view of your system's health. To install our default dashboards, go to our Ansible Automation Controller instant observability page).
To learn more about building NRQL queries and generating dashboards, check out these docs: