# SQL listener in Synthetic Monitoring

**URL:** <https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217>\
**Category:** Synthetic Monitoring\
**Tags:** sql, synthetic-monitoring\
**Created:** [September 3, 2025, 1:07pm UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217 "2025-09-03T13:07:28Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![MikeL](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@MikeL](https://community.dynatrace.com/u/MikeL)\
**Post date:** [September 3, 2025, 1:07pm UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217/1 "2025-09-03T13:07:28Z")

</div>

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.&nbsp;  
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&nbsp; **HTTPs: // SQLlistenerURL** &nbsp; **. 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,&nbsp; it would seems obvious but here we are or we are missing something?

Thx folks for any clarity the community can provide.

---

<div class="post-metadata">

**Author:** ![p\_devulapalli](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/p_devulapalli/32/41590_2.png) [@p\_devulapalli](https://community.dynatrace.com/u/p_devulapalli)\
**Post date:** [September 5, 2025, 12:34am UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217/2 "2025-09-05T00:34:44Z")

</div>

[@MikeL](https://community.dynatrace.com/user/84268)&nbsp;Have you considered using a NAM monitor instead ?

---

<div class="post-metadata">

**Author:** ![MikeL](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@MikeL](https://community.dynatrace.com/u/MikeL)\
**Post date:** [September 8, 2025, 2:31pm UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217/3 "2025-09-08T14:31:59Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![mizso74](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mizso74/32/41729_2.png) [@mizso74](https://community.dynatrace.com/u/mizso74)\
**Post date:** [September 8, 2025, 8:55pm UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217/4 "2025-09-08T20:55:40Z")

</div>

Hi&nbsp;[@MikeL](https://community.dynatrace.com/user/84268),

Here is the documentation link:

[Network availability monitoring — Dynatrace Docs](https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/network-availability-monitors/network-availability-monitoring)

There are some examples:

[Synthetic - Demo Live (demo) - Dynatrace](https://guu84124.apps.dynatrace.com/ui/apps/dynatrace.synthetic/monitors?from=now%28%29-2h&to=now%28%29)

 ![Mizs_1-1757364911347.png](https://global.discourse-cdn.com/dynatrace/original/3X/9/0/9080e611b32c9e0f74c765c33931f0f4b29f1173.png)

[Synthetic - Demo Live (demo) - Dynatrace](https://guu84124.apps.dynatrace.com/ui/apps/dynatrace.synthetic/edit/MULTIPROTOCOL_MONITOR-3A3F3A79A47DED0C?from=now%28%29-2h&to=now%28%29)

 ![Mizs_0-1757364829245.png](https://global.discourse-cdn.com/dynatrace/original/2X/c/c176fba31b31a8111753fb96cfda003605b7570d.png)

[Synthetic - Dynatrace Playground - Dynatrace](https://wkf10640.apps.dynatrace.com/ui/apps/dynatrace.synthetic/monitors?from=now%28%29-2h&to=now%28%29)

I hope it helps.

Best regards,

János

---

<div class="post-metadata">

**Author:** ![MikeL](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@MikeL](https://community.dynatrace.com/u/MikeL)\
**Post date:** [September 8, 2025, 9:41pm UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217/5 "2025-09-08T21:41:05Z")

</div>

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

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

---

<div class="post-metadata">

**Author:** ![p\_devulapalli](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/p_devulapalli/32/41590_2.png) [@p\_devulapalli](https://community.dynatrace.com/u/p_devulapalli)\
**Post date:** [September 9, 2025, 2:32am UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217/6 "2025-09-09T02:32:04Z")

</div>

[@MikeL](https://community.dynatrace.com/user/84268)&nbsp;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

 ![p_devulapalli_0-1757385065309.png](https://global.discourse-cdn.com/dynatrace/original/3X/2/9/2968f233415a948be700ac57bd0398b433dd1f5b.png)

---

<div class="post-metadata">

**Author:** ![MikeL](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@MikeL](https://community.dynatrace.com/u/MikeL)\
**Post date:** [October 6, 2025, 12:51pm UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217/7 "2025-10-06T12:51:37Z")

</div>

Thx, we managed to add our new cross site SQL listener IP working via NAM.&nbsp; Thx for that lead Phani.&nbsp; Now to get that SQL node to failover per site then over to the other data center to see if DT picks that up 🙂

 ![Dynatrace NAM SQL Listener.jpg](https://global.discourse-cdn.com/dynatrace/original/3X/0/5/05f7b8ce0ecd1e8bd98f804dd47e83316aefa50d.jpeg)

---

<div class="post-metadata">

**Author:** ![MikeL](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@MikeL](https://community.dynatrace.com/u/MikeL)\
**Post date:** [October 6, 2025, 1:01pm UTC](https://community.dynatrace.com/t/sql-listener-in-synthetic-monitoring/53217/8 "2025-10-06T13:01:16Z")

</div>

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&nbsp; “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.&nbsp; Ideas anyone?

 ![Dynatrace NAM SQL Listener Constraint Violated.jpg](https://global.discourse-cdn.com/dynatrace/original/2X/2/26cecdbdf85e99eb90808d65a0bd707bf6ab3948.jpeg)  
 ![Dynatrace NAM SQL Listener Success.jpg](https://global.discourse-cdn.com/dynatrace/original/3X/0/3/035b7e2c6ea59c8e5ae0071768887c503379892a.jpeg)
