What’s new: Updates for automation dashboard

Updated -

The automation dashboard utility is generally available as part of the Ansible Automation Platform subscription. Connect automation dashboard to one or more Ansible Automation Platform deployments to visualize automation usage data, determine time savings, track ROI, and drive increased visibility into automation strategy, resource allocation, and prioritization of automation projects.

Enhancements

The following enhancements were added to the automation dashboard on March 11th, 2026.

  • ROI and Reporting:
    • Subscription-based Costing: Refactored the cost model to track Monthly AAP subscription costs and average engineer hourly rates, replacing legacy per-minute automated tracking. The system now prorates these monthly costs into daily values for more accurate ROI reporting.
    • Mandatory PDF Date Ranges: Updated the PDF export process to require a start and end date selection, ensuring that exported reports contain a defined and accurate data set.
  • Security:
    • The system now automatically deletes the clusters.yaml configuration file from the container's /tmp/ directory after successful processing. This prevents sensitive credentials from remaining on the container.
  • Installation:
    • Added the registry_url_aap_automation_dashboard and registry_ns_aap_automation_dashboard inventory variables. You can configure these variables to pull automation dashboard images from a different registry or namespace than your database and Redis images.

The following enhancements were added to the automation dashboard on January 14th, 2026.

  • Metrics integration:
    • Added a Prometheus-compatible metrics subsystem for advanced monitoring.
  • API and documentation:
    • Added OpenAPI schema generation and authenticated documentation.
  • User experience:
    • Updated manual job cost input from "per minute" to an "hourly rate."
    • Optimized initial page loading with dedicated endpoints for labels, projects, and organizations.
    • Added a system-wide mechanism to reset user inputs to default values with validation.
    • Automated calculation of manual execution time when no job history exists.

Fixed issues

The following issues were fixed within the automation dashboard on March 11th, 2026.

Installation and deployment:

  • Resolved an issue where the installation program failed with module resolution errors on a clean system. You must now run the ansible-galaxy collection install -r requirements.yml command to explicitly install the required Ansible collections before running the installation playbook.

The following issues were fixed within the automation dashboard on January 14th, 2026.

  • Installation and deployment:
    • Corrected the default port to 443 in the cluster configuration.
    • Fixed the application icon (favicon) display issue.
  • Data and syncing:
    • Fixed duplicate entries created during data synchronization.
    • Fixed synchronization process failure when it could not prompt the user for confirmation.
  • Cluster management:
    • Improved the getclusters command to filter schedules per cluster.
  • User management:
    • Fixed user creation processes to properly assign and handle auditor roles.
  • Logging and reporting:
    • Updated logging levels to show "WARNING" instead of "ERROR" for non-critical events.
    • Fixed an issue with PDF downloads and implemented clearer error messages for exceeding maximum limits.
    • Enhanced logging for authentication and user management modules.

Step-by-step process for reporting issues

If you encounter an issue while using automation dashboard, follow these steps to report it to the engineering team:

  1. Capture logs: Run the following command to gather authentication and system logs: journalctl --user-unit automation-dashboard* --user-unit postgresql --user-unit redis* > dashboard_logs.txt
  2. Verify configuration: Check your clusters.yaml file to ensure all variables are correctly defined and that the port is set to 443.
  3. Submit a ticket: Open a support case using Customer support and attach your dashboard_logs.txt and a screenshot of the error.

Related Documentation

Comments