SQL listener & Synthetic monitoring

[MikeL]

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. 

[p_devulapalli]

@MikeL Have you considered using a NAM monitor instead ?

[MikeL]

No, we are just early adopters. Could you provide a detailed example of config and expected results for comparison.  Much appreciated.

[Mizső]

Hi @MikeL,

Here is the documentation link:

Network availability monitoring — Dynatrace Docs

There are some examples:

Synthetic - Demo Live (demo) - Dynatrace

Synthetic - Demo Live (demo) - Dynatrace

Synthetic - Dynatrace Playground - Dynatrace

I hope it helps.

Best regards,

János

[MikeL]

Thx, 
What would that actually look like visually once setup?  could you provide a screen shot?

1st & 2nd demo link, 403 You don't have permission to view this page

 

[p_devulapalli · Accepted solution]

@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  

Playground 

[MikeL]

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 🙂

[MikeL]

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?