DocumentationExperience Cloud KCS

Integrate Dynatrace and ELK with Adobe Experience Manager as a Cloud Service

Last update: October 21, 2026

This article explains how to integrate Dynatrace APM and log forwarding with Adobe Experience Manager as a Cloud Service. Use the documented log-forwarding configuration and a Cloud Manager Config Pipeline to send AEM logs to Dynatrace, Elasticsearch/OpenSearch, or a compatible HTTPS destination. Dynatrace APM follows a separate integration process. To configure these integrations, confirm the prerequisites, protect the required secrets, deploy the configuration, and verify telemetry in the target monitoring system.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • Cloud Manager Config Pipeline
  • Dynatrace APM or AEM log forwarding to Dynatrace, Elasticsearch/OpenSearch, or a compatible HTTPS destination

Issue/Symptoms

  • You need to monitor an AEM as a Cloud Service environment with Dynatrace Application Performance Monitoring.
  • You need to forward AEM logs to Dynatrace or an Elasticsearch/OpenSearch-based log-analysis system.

Cause

AEM as a Cloud Service uses separate configuration paths for application performance monitoring and log forwarding. Log forwarding is configured in Git with a LogForwarding YAML file and deployed through a Cloud Manager Config Pipeline. Dynatrace APM uses a separate documented connectivity process. An ELK architecture requires a supported Elasticsearch/OpenSearch or HTTPS ingestion path.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Confirm the prerequisites:

    • Verify that you have access to Cloud Manager and the permissions required to update configuration pipelines.
    • Obtain the required configuration details from your Dynatrace or ELK environment, such as the ingest endpoint and authentication requirements.

    Note: Store authentication tokens as Cloud Manager secret environment variables. Don’t commit tokens, passwords, or other secrets to Git.

  2. Determine which integration you need:

    • Dynatrace log forwarding.
    • Dynatrace APM.
    • Elasticsearch/OpenSearch-based log forwarding for an ELK architecture.
    • A combination of log forwarding and APM.

    Note: Log forwarding and Dynatrace APM are separate integrations. Configuring one doesn’t automatically configure the other.

  3. Set up log forwarding to Dynatrace or an ELK-compatible destination:

    • Define the supported LogForwarding configuration in your Git repository according to the selected destination.
    • For Elasticsearch/OpenSearch, use the documented Elasticsearch/OpenSearch destination configuration.
    • For Dynatrace, use the supported HTTPS log-ingestion configuration when your Dynatrace endpoint accepts the required format and authentication.
    • Commit and push the configuration changes.
    • Deploy the configuration with a targeted Cloud Manager Config Pipeline.

    Note: The Config Pipeline deploys the YAML configuration to the selected environment. A full-stack or web-tier pipeline doesn’t deploy a log-forwarding configuration file.

  4. Integrate Dynatrace APM separately:

    • Follow the documented Dynatrace APM integration process for AEM as a Cloud Service.
    • Use the Adobe support-request process when the documented integration requires Adobe-side connectivity setup.

    Note: Enabling Dynatrace APM disables Adobe-provided New Relic APM data collection for that environment. Log forwarding remains a separate configuration path.

  5. Verify the integrations after deployment:

    • Confirm that logs arrive in Dynatrace or the selected Elasticsearch/OpenSearch-based log-analysis system.
    • For Dynatrace APM, confirm that Dynatrace collects application performance data from the AEM as a Cloud Service environment.

  6. If data isn’t available, troubleshoot the applicable integration:

    • For log forwarding, review the YAML configuration, endpoint, authentication reference, and Cloud Manager pipeline result.
    • Confirm that the endpoint is reachable and that the vendor-side ingest configuration accepts the forwarded logs.
    • For Dynatrace APM, confirm that the Dynatrace integration is active and that Adobe-provided New Relic APM is no longer collecting data for the environment.

    Note: Don’t include authentication tokens or private endpoints in logs, screenshots, Git commits, or support attachments.

recommendation-more-help
experience-cloud-kcs-help-kbarticles