# Management Zone Name inside Webhook Payload

**URL:** <https://community.dynatrace.com/t/management-zone-name-inside-webhook-payload/21282>\
**Category:** Alerting\
**Tags:** management-zones, problems-classic\
**Created:** [January 21, 2021, 1:28pm UTC](https://community.dynatrace.com/t/management-zone-name-inside-webhook-payload/21282 "2021-01-21T13:28:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![serhat\_balik](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@serhat\_balik](https://community.dynatrace.com/u/serhat_balik)\
**Post date:** [January 21, 2021, 1:28pm UTC](https://community.dynatrace.com/t/management-zone-name-inside-webhook-payload/21282/1 "2021-01-21T13:28:09Z")

</div>

There are multiple placeholders to send with webhook such as {ImpactedEntity}, {Tags}, etc..

But I couldn’t find a way to send Manage Zone Name of the impacted entities. Do you guys have ever tried to tackle this problem?

---

<div class="post-metadata">

**Author:** ![Babar\_Qayyum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/babar_qayyum/32/13620_2.png) [@Babar\_Qayyum](https://community.dynatrace.com/u/Babar_Qayyum)\
**Post date:** [January 21, 2021, 1:51pm UTC](https://community.dynatrace.com/t/management-zone-name-inside-webhook-payload/21282/2 "2021-01-21T13:51:44Z")

</div>

Hello [@MUSTAFA SERHAT B.](https://answers.dynatrace.com/users/41751/view.html)

The placeholder is not available at the moment to explicitly define the management zone in the subject/message of the email incident.

Regards,

Babar

---

<div class="post-metadata">

**Author:** ![JamesKitson](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jameskitson/32/22460_2.png) [@JamesKitson](https://community.dynatrace.com/u/JamesKitson)\
**Post date:** [January 21, 2021, 2:12pm UTC](https://community.dynatrace.com/t/management-zone-name-inside-webhook-payload/21282/3 "2021-01-21T14:12:51Z")

</div>

Keep in mind that management zones can overlap, a given host can be in multiple management zones and that must be accounted for. Depending on what you’re trying to do if the notification is filtered to a single management zone you could just ‘hardcode’ the management zone name into the payload. Otherwise perhaps just creating corresponding tags would be an option.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [January 26, 2021, 8:18am UTC](https://community.dynatrace.com/t/management-zone-name-inside-webhook-payload/21282/4 "2021-01-26T08:18:20Z")

</div>

Still, a placeholder of an array of management zones could be useful in some use cases. Typically tags and MZ are might have similar scop in the deployments, but they are not interchangable.

---

<div class="post-metadata">

**Author:** ![serhat\_balik](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@serhat\_balik](https://community.dynatrace.com/u/serhat_balik)\
**Post date:** [January 29, 2021, 10:11am UTC](https://community.dynatrace.com/t/management-zone-name-inside-webhook-payload/21282/5 "2021-01-29T10:11:24Z")

</div>

Thank you guys for the answers. We will go with Manual payload option for now.

If you don’t mind I want to ask two more related questions. We’re moving from AppDynamics to Dynatrace and we’re integrating this with BMC Truesight.

**1.** {impactedEntity} sends a message something like “CPU increase at _abcHost_”

We just want to send the _abcHost_ part. The explanation part is redundant in our situation, and I couldn’t wrap my head around how to get this part from the other option {impactedEntities} JSON list.

**2.** It is possible to use logical syntax in AppDynamics which helps to send _Event_ type that is more compatible with BMC. In Dynatrace I immediately get a syntax error when I try something like the code below.

```auto
[<br>{<br>"eventSourceHostName": "APMTEST",<br>"eventSourceIPAddress": "xx.xx.xx.xx",<br>#if(${latestEvent.node.name})<br>"eventSourceHostName": "${latestEvent.node.name}",<br>"eventSourceIPAddress": "",<br>#end<br>"attributes": {<br>"CLASS": "APM_EV",<br>"controllerUrl": "${controllerUrl}",<br>"accountId": "${account.id}",<br>"accountName": "${account.name}",<br>"mc_object": "${latestEvent.tier.name}",<br>"mc_object_uri": "${latestEvent.deepLink}",<br>#if(${latestEvent.healthRule.name})<br>"mc_parameter": "${latestEvent.healthRule.name}",<br>"mc_tool": "${latestEvent.healthRule.name}_${latestEvent.severity}",<br>"mc_smc_alias": "${latestEvent.healthRule.name}",<br>#end<br>"mc_service": "${latestEvent.application.name}",<br>"mc_priority": "PRIORITY_1",<br>#if(${latestEvent.severity}=="ERROR") ---->> <strong>HOW CAN WE WRITE THIS?<br></strong>"severity": "CRITICAL",<br>#end<br>#if(${latestEvent.severity}=="WARN") ---->> <strong>HOW CAN WE WRITE THIS?<br></strong>"severity": "MAJOR",<br>#end<br>#if(${latestEvent.severity}=="INFO") ---->> <strong>HOW CAN WE WRITE THIS?<br></strong>"severity": "OK",<br>#end<br>"msg": "$!{latestEvent.summaryMessage.replace('<br>',' ').replace('<b>','').replace('</b>','')}",<br>"mc_long_msg": "$!{latestEvent.eventMessage.replace('<br>',' ').replace('<b>','').replace('</b>','')}"<br>}<br>}<br>]

```
