Would anyone know the proper syntax to use when adding a Synthetic endpoints, then adding both IP & Listener URL both using port 1433, to be monitored.
in our case we’d like to both DNS & IP to be monitored. Here’s an example.
2 HTTP requests
1 Request = Get Method & set details to HTTPs: // SQLlistenerURL. domain.ca : 1433 or SQLlistenerURL . domain.ca : 1433
2 Request = Get Method & set IP = 10.10.10.x : 1433
Q1: What are others using for the request HTTP syntax that avoids the Failed requests = “Target URL is invalid”, since we tried many, & On-Demand gets a Failure = “MALCORMED_URL_ERROR” (same in Execution details = “healthStatus”: “MALFORMED_URL_ERROR”), regardless if its an IP or URL, it would seems obvious but here we are or we are missing something?
Thx folks for any clarity the community can provide.
@MikeL First two links are from demo instance which not everyone might have access to , you should still be able to get to the playground instance and have a look
Thx, we managed to add our new cross site SQL listener IP working via NAM. Thx for that lead Phani. Now to get that SQL node to failover per site then over to the other data center to see if DT picks that up
Oddly some SQL clusters that are in the same rack, subnet, etc with verified FW flows (Telnet & PortQry) to each one from each AG to SQL listener IP shows, showing “CONSTRAINT_VIOLATED” & under events we see “dt.event.synthetic_outage_details …[object Object]”, if we add more AG’s, that simply adds one “[object Object]” per AG.
FW team confirmed something is closing that session, can’t quite figure out if that the listener or Node handling it in the back end. Ideas anyone?