Dynatrace process group naming reverts to default in Adobe Experience Manager as a Cloud Service
Adobe Experience Manager as a Cloud Service (AEMaaCS) environments monitored through Dynatrace may experience process group names reverting to default values, causing multiple environments to appear under the same process group. This issue is typically related to Dynatrace configuration or detection logic and can result in false alerts, monitoring inconsistencies, and pods appearing inactive or not reporting data. To resolve the issue, review Dynatrace configuration and restore the intended process group naming.
Description description
Environment
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- Development, Stage, and Production
Issue/Symptoms
- Dynatrace process group names revert to default values across multiple environments.
- Multiple environments report under the same process group name in Dynatrace.
- False alerts are triggered due to overlapping process group names.
- Some pods appear as inactive and do not report data to Dynatrace.
Root cause
The issue is typically caused by changes or issues within Dynatrace configuration or detection logic, not by AEM as a Cloud Service infrastructure or deployments.
Resolution resolution
Follow the steps below to resolve the issue:
- Confirm whether the issue is limited to Dynatrace process group naming or whether telemetry (metrics, logs, transactions) has also stopped for affected pods.
- Check with your Dynatrace administrators to determine whether any changes were made to naming rules, detection rules, tags, management zones, or tenant configuration around the time the issue began.
- Review the Dynatrace OneAgent version and ensure that it is consistent across all affected pods.
- Gather and compare process group IDs, entity IDs, and naming conventions before and after the issue for affected pods (for example, screenshots or exports from Dynatrace).
- If the issue is confirmed to originate from Dynatrace configuration or detection logic, coordinate with your Dynatrace administrators to restore the intended process group naming.
- If no changes were made on the Dynatrace side and the issue persists, collect relevant logs, telemetry details, and process group information, then contact Adobe Support for further investigation.
- Verify the resolution by confirming that process group names in Dynatrace are restored to their intended values and that all pods are reporting data as expected.
recommendation-more-help
experience-cloud-kcs-help-kbarticles