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.

$
touch /home/ansible-automation-patform/bearer_token_file

And paste your token in the created file.

$
nano /home/ansible-automation-platform/bearer_token_file
$
<paste your token>

Save and exit the nano editor

First, create a file named “nri-prometheus-config.yml” in the path below:

Path: /etc/newrelic-infra/integrations.d/nri-prometheus-config.yml

Then, use our configuration template to update the created file named "nri-prometheus-config.yml."

Now, update the fields listed below:

1. cluster_name: "YOUR_DESIRED_CLUSTER_NAME"

2. bearer_token_file: "BEARER_TOKEN_FILE_PATH"

3. urls: ["https://YOUR_HOST_IP:443/api/v2/metrics/?format=txt"]

4. Insecure_skip_verify: true

   Your nri-prometheus-config.yml file should look like this:

   integrations:

   Copy

• name: nri-prometheus config:

  When standalone is set to false nri-prometheus requires an infrastructure agent to work and send data. Defaults to true

  standalone: false

  When running with infrastructure agent emitters will have to include infra-sdk

  emitters: infra-sdk

  The name of your cluster. It's important to match other New Relic products to relate the data.

  cluster_name: "YOUR_DESIRED_CLUSTER_NAME" bearer_token_file: "BEARER_TOKEN_FILE_PATH"

  targets:

  • description: Metrics of Ansible Automation Platform can be seen on the below url urls: ["https://YOUR_HOST_IP:443/api/v2/metrics/?format=txt"] use_bearer: true

    tls_config:

    ca_file_path: "/etc/etcd/etcd-client-ca.crt"

    cert_file_path: "/etc/etcd/etcd-client.crt"

    key_file_path: "/etc/etcd/etcd-client.key"

    Whether the integration should run in verbose mode or not. Defaults to false.

    verbose: 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.

    audit: true

    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.

    scrape_duration: "5s"

    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.

    insecure_skip_verify: true

    timeout: 10s

  Copy

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:

Path: /etc/newrelic-infra/logging.d/

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
  file: /var/log/tower/tower.log
  attributes:
    logtype: 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'