# Problem notifications with internal webhook after migration

**URL:** <https://community.dynatrace.com/t/problem-notifications-with-internal-webhook-after-migration/38384>\
**Category:** Upgrade To Saas\
**Tags:** upgrade-to-saas\
**Created:** [February 10, 2023, 7:57am UTC](https://community.dynatrace.com/t/problem-notifications-with-internal-webhook-after-migration/38384 "2023-02-10T07:57:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MaciejNeumann](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@MaciejNeumann](https://community.dynatrace.com/u/MaciejNeumann)\
**Post date:** [February 10, 2023, 7:57am UTC](https://community.dynatrace.com/t/problem-notifications-with-internal-webhook-after-migration/38384/1 "2023-02-10T07:57:13Z")

</div>

How can we manage the problem notification with an internal webhook after the Saas migration?

---

<div class="post-metadata">

**Author:** ![Radoslaw\_Szulgo](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radoslaw_szulgo/32/1977_2.png) [@Radoslaw\_Szulgo](https://community.dynatrace.com/u/Radoslaw_Szulgo)\
**Post date:** [February 10, 2023, 4:45pm UTC](https://community.dynatrace.com/t/problem-notifications-with-internal-webhook-after-migration/38384/2 "2023-02-10T16:45:37Z")

</div>

With Dynatrace, a problem notification is possible only if a webhook endpoint is exposed on public access. You can safeguard this endpoint by exposing it behind a proxy server placed in a DMZ network.

If that’s not possible, then please wait until we share the solution requested in that product idea:

[https://community.dynatrace.com/t5/Dynatrace-product-ideas/RFE-Dynatrace-Saas-and-webhook-integration-with-private-access/idc-p/200818#M34512](https://community.dynatrace.com/post/200818)

Alternatively, you can develop an extension that polls problems from Dynatrace and injects them into your ITSM systems.