topic Bidirectional Synthetic Monitoring (cloud evni ↔ OnPrem) and Correlated Alerting Best Practice in Open Q&A https://community.dynatrace.com/t5/Open-Q-A/Bidirectional-Synthetic-Monitoring-cloud-evni-OnPrem-and/m-p/303109#M39378 <P>We are designing bidirectional synthetic monitoring where:</P><UL><LI>AWS environment monitors 2 endpoints hosted in OnPrem</LI><LI>OnPrem environment monitors 2 endpoints hosted in AWS</LI></UL><P>We are evaluating the best monitoring approach:</P><UL><LI>DNS Network Monitor</LI><LI>TCP Network Monitor</LI><LI>HTTP GET</LI><LI>HTTP POST (transaction validation)</LI></UL><P>One view is that DNS validation is sufficient since every HTTP/TCP request requires DNS resolution and some cloud-native workloads (e.g., Kubernetes/EKS) may have dynamic backend IPs. Another view is that DNS-only monitoring doesn't truly validate traffic flow, application reachability, or service availability. <STRONG><U>"We are goona use Private AG for the configuration - suggest best prectice(the requirements is like - to validate the flow from each DC to another DC hosted urls,api - major thing is to validate the flow is up and running) and also suggest if we configure the url-api for synthetic endpoint with get call then which code can be used so it can denote the network flow or traffic is not right like 504 only? do suggest."</U></STRONG></P><H3>Questions</H3><OL><LI><P>From a Dynatrace architecture perspective, what is the recommended approach for validating cross-environment flow and availability?</P><UL><LI>DNS</LI><LI>TCP</LI><LI>HTTP GET</LI><LI>HTTP POST</LI><LI>Combination of approaches</LI></UL></LI><LI><P>Is DNS-only monitoring considered sufficient for availability validation, or should it only be a supporting signal?</P></LI><LI><P>For cloud-native applications where backend IPs change frequently, is hostname-based monitoring via HTTP/TCP the preferred approach?</P></LI><LI><P>We want to create a <STRONG>single problem card</STRONG> only when:</P><UL><LI>Multiple synthetic endpoints fail (4 endpoints across 2 environments)</LI><LI>A related service simultaneously shows elevated failure/error rates</LI></UL></LI></OL><P>What is the recommended correlation approach in Dynatrace?</P><UL><LI>Davis AI</LI><LI>Metric Events / Anomaly Detection</LI><LI>DQL Events</LI><LI>Workflows</LI><LI>Combination of the above</LI></UL><P>Looking for best practices and real-world implementations.</P> Tue, 11 Aug 2026 16:23:08 GMT gauravpayghan 2026-08-11T16:23:08Z Bidirectional Synthetic Monitoring (cloud evni ↔ OnPrem) and Correlated Alerting Best Practice https://community.dynatrace.com/t5/Open-Q-A/Bidirectional-Synthetic-Monitoring-cloud-evni-OnPrem-and/m-p/303109#M39378 <P>We are designing bidirectional synthetic monitoring where:</P><UL><LI>AWS environment monitors 2 endpoints hosted in OnPrem</LI><LI>OnPrem environment monitors 2 endpoints hosted in AWS</LI></UL><P>We are evaluating the best monitoring approach:</P><UL><LI>DNS Network Monitor</LI><LI>TCP Network Monitor</LI><LI>HTTP GET</LI><LI>HTTP POST (transaction validation)</LI></UL><P>One view is that DNS validation is sufficient since every HTTP/TCP request requires DNS resolution and some cloud-native workloads (e.g., Kubernetes/EKS) may have dynamic backend IPs. Another view is that DNS-only monitoring doesn't truly validate traffic flow, application reachability, or service availability. <STRONG><U>"We are goona use Private AG for the configuration - suggest best prectice(the requirements is like - to validate the flow from each DC to another DC hosted urls,api - major thing is to validate the flow is up and running) and also suggest if we configure the url-api for synthetic endpoint with get call then which code can be used so it can denote the network flow or traffic is not right like 504 only? do suggest."</U></STRONG></P><H3>Questions</H3><OL><LI><P>From a Dynatrace architecture perspective, what is the recommended approach for validating cross-environment flow and availability?</P><UL><LI>DNS</LI><LI>TCP</LI><LI>HTTP GET</LI><LI>HTTP POST</LI><LI>Combination of approaches</LI></UL></LI><LI><P>Is DNS-only monitoring considered sufficient for availability validation, or should it only be a supporting signal?</P></LI><LI><P>For cloud-native applications where backend IPs change frequently, is hostname-based monitoring via HTTP/TCP the preferred approach?</P></LI><LI><P>We want to create a <STRONG>single problem card</STRONG> only when:</P><UL><LI>Multiple synthetic endpoints fail (4 endpoints across 2 environments)</LI><LI>A related service simultaneously shows elevated failure/error rates</LI></UL></LI></OL><P>What is the recommended correlation approach in Dynatrace?</P><UL><LI>Davis AI</LI><LI>Metric Events / Anomaly Detection</LI><LI>DQL Events</LI><LI>Workflows</LI><LI>Combination of the above</LI></UL><P>Looking for best practices and real-world implementations.</P> Tue, 11 Aug 2026 16:23:08 GMT https://community.dynatrace.com/t5/Open-Q-A/Bidirectional-Synthetic-Monitoring-cloud-evni-OnPrem-and/m-p/303109#M39378 gauravpayghan 2026-08-11T16:23:08Z