OneAgent-to-ActiveGate routing precedence during gateway outage

When instrumenting a small application with Dynatrace OneAgent the integration boundary with ActiveGate determines how telemetry reaches the Dynatrace cluster OneAgent can be configured to send data through an ActiveGate proxy or connect directly to the cluster and the active path influences both monitoring continuity and network topology The precise goal is to establish whether OneAgent will automatically fail over to a secondary ActiveGate revert to direct-cluster connectivity or cease reporting when the primary ActiveGate becomes unavailable and how this behavior interacts with rolling-restart requirements for full deep monitoring Key uncertainty surrounds version-specific failover semantics and the absence of documented seamless switchover without manual reconfiguration Does OneAgent prioritize the configured ActiveGate endpoint fall back to a list of configured gateways or switch to direct cluster endpoints upon gateway loss? How does the chosen mode affect firewall rule stability and host-unit licensing consumption during the migration window?