Log forwarding endpoint reverts after AEM rollout in AEMaaCS
Adobe Experience Manager as a Cloud Service (AEMaaCS) reverts the log forwarding configuration to a previous endpoint following a rollout. This causes logs to be sent to an outdated destination instead of the intended Azure Front Door (AFD) telemetry endpoint. To resolve the issue, run the configuration pipeline after updating the settings.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
- Log data stops reaching the intended Azure Front Door (AFD) telemetry endpoint.
- Logs are forwarded to a previously configured endpoint instead of the updated one.
- The issue appears consistently across all programs immediately after an AEM rollout.
Resolution resolution
Follow the steps below to resolve the issue:
- Open the
LogForwarding.yamlfile and confirm the correct endpoint is specified. - Check whether a configuration pipeline run has occurred since the last update.
- If no pipeline run is detected, initiate a configuration pipeline to apply the changes.
- After the pipeline completes, verify that logs are reaching the correct AFD endpoint.
Note: Changes made directly in code or configuration files without running the pipeline won’t take effect and will revert during rollouts.
Related reading
- Log Forwarding in the AEM as a Cloud Service User Guide
- Use config pipelines in the AEM as a Cloud Service User Guide
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f