1. What is the nature and description of the request?

Add native support for Dynatrace as a Logging Aggregator target in Ansible Automation Platform (AAP), similar to existing supported integrations such as Splunk, Loggly, Sumo Logic, and Elastic Stack.

Currently, customers integrating AAP with Dynatrace must rely on custom rsyslog configurations (for example, using omhttp and manual proxy handling). This approach works but is not officially supported, may be overwritten during upgrades, and introduces operational risk.

The request is to make Dynatrace a first-class, supported logging destination within the AAP Logging Aggregator configuration.

2. Why does the customer need this? (Business requirements)

• • Enterprise standardization: Dynatrace is a widely adopted, enterprise-grade observability platform and is the strategic logging and monitoring solution for many organizations.

• • SaaS migration: Customers are migrating away from on-prem tools (Splunk, OBM) to Dynatrace SaaS, and need AAP to integrate seamlessly.

• • Operational continuity: Logging is critical for auditing, troubleshooting, and compliance. Unsupported custom solutions risk breaking during upgrades.

• • Upgrade safety: Native support ensures logging configurations persist across AAP patches and version upgrades.

• • Security & governance: Centralized, supported configuration reduces the need for manual service-level modifications and custom tokens embedded in config files.

    3. How would you like to achieve this? (Functional requirements)

• • Add Dynatrace as a selectable option in the AAP Logging Aggregator UI

• • Provide configuration fields for:

• • • Dynatrace environment URL

• • • Log ingest API endpoint

• • • API token (secured via AAP credentials)

• • • HTTPS support

• • • HTTP/HTTPS proxy configuration

• • Support Dynatrace's log ingest API (v2) natively

• • Ensure configurations are:

• • • Upgrade-safe

• • • Fully supported by Red Hat

• • • Documented in official AAP documentation