Dynatrace host monitoring and tagging missing for additional AEM publish region
This article explains how to troubleshoot and resolve the issue where an additional Adobe Experience Manager (AEM) publish region is not reporting host metrics or tags in Dynatrace, even though log forwarding is working.
Description description
Environment
- Adobe Experience Manager (all versions)
- Dynatrace monitoring with OneAgent deployed to AEM publish pods
Issue/Symptoms
When you add a new publish region to your AEM deployment, you may find that while logs from publish pods forward successfully to Dynatrace, host-level monitoring and tagging are incomplete. The primary region appears in Dynatrace with full host metrics, tags, and topology, but the additional region does not. This can impact dashboards and alerting that rely on host metrics and tags.
- Log forwarding from publish pods in the additional region is visible in Dynatrace.
- Host entities from the additional region do not appear in Dynatrace host/infrastructure monitoring, or appear but report zero metrics (CPU, memory, etc.).
- No process group instances are present for these hosts.
- Auto-tagging rules are not applied to hosts in the additional region, while primary region hosts are tagged.
- The additional region is live and serving traffic.
- Only publish pods are present in the additional region; Author pods and Dispatcher monitoring are not in scope.
Cause
The additional publish region’s hosts are not fully onboarded into Dynatrace host monitoring due to configuration, licensing, or tagging gaps. This results in missing metrics, topology visibility, and tags.
Resolution resolution
Follow these steps to resolve the issue:
- Verify that Dynatrace OneAgent is installed and running on all publish pods in the additional region. The OneAgent state for each host should be
RUNNING. - Check Dynatrace host-unit licensing and monitoring capacity to ensure there are available resources for the additional region’s hosts. If licensing is exhausted, new hosts may not report metrics or appear in topology.
- In Dynatrace, confirm that the new region’s hosts are not in a Monitoring off state and that OneAgent is not running in discovery-only mode. Compare with the primary region’s host settings.
- Review and update auto-tagging rules in Dynatrace to ensure that hosts from the additional region are included. This ensures dashboards and alerts include the new region.
- Confirm that process group detection is configured for publish pods in the additional region. If process groups are missing, review OneAgent configuration and Dynatrace process detection rules.
- After making these changes, verify in Dynatrace that host entities from the additional region appear with active metrics and correct tags.