3766769 - "Requests to unmonitored hosts" in Dynatrace trace when request does not reach the application pod

In Dynatrace, a distributed trace for a failed request shows the Apache webserver as the top-level service, with the downstream hop labeled "Requests to unmonitored hosts" rather than the expected service on the downstream application pod such as api, backoffice, backgroundprocessing or accstorefront. The request does not appear in application-level logs on the downstream pod, and no matching trace is visible in Dynatrace for that downstream service. The total trace duration is short, typically in the range of tens to hundreds of milliseconds, and the contribution time of Apache modules accounts for the majority or entirety of the trace. The response status visible in the trace reflects an error code, most commonly 502 Bad Gateway or 400 Bad Request.

SAP Commerce Cloud

SAP Commerce Cloud, Dynatrace, unmonitored hosts, requests to unmonitored hosts, Apache, mod_proxy, apache2, AH01102, 502, 502 Bad Gateway, keep-alive, connectionTimeout, ccv2.platform.tomcat.serverxml.connectionTimeout, Tomcat, Tomcat connector, connection pool, race condition, Internal error, 20014, OpenSearch, apache2 pod logs, mod_security2, 400 Bad Request, maxHttpHeaderSize, ccv2.platform.tomcat.serverxml.maxHttpHeaderSize, reverse proxy, trace, distributed trace, api pod, backoffice pod, storefront pod, backgroundprocessing pod, FIN, half-closed socket, intermittent 502, WAF, proxy, webserver , KBA , CEC-SCC-PLA-PL , Platform , Problem