We recently ran into a situation here the requests to unmonitored hosts jumped and has stayed there. This was noticed by some folks in AppDev when they were chasing some purepaths and found many broken chains. Some research indicated that "something" happened on 12/10/20 around 4:00AM. See chart below. Has anyone run into this type of situation? Of course "nothing" has changed. 🙂
Could it be that there's a component (LB/proxy/integration service/etc.) that's stripping the x-dynatrace headers, in effect terminating the PurePaths and making those requests look like they're towards unmonitored hosts? So for example connections towards domain names which resolve to load balancer VIPs and as such do not correspond to any specific server with OneAgent running..?
Another solid question and that is where we have been concentrating. The issue seems to be surrounding calls in/out of our Web Service Managed infrastructure that is front-ended by a LB. We are full y running in AWS on a mix of EC2 and Native Svcs and the ELB in this case is a CLB. We have reviewed changes at the time of the spike (approx. 12/10 at 4:00AM ) and there were no scheduled changes by our organization at that time.