# Exempt specific nodes from target alerts

**URL:** <https://community.netbeez.net/t/exempt-specific-nodes-from-target-alerts/222>\
**Category:** Network Agents\
**Tags:** pagerduty\
**Created:** [August 8, 2024, 2:18pm UTC](https://community.netbeez.net/t/exempt-specific-nodes-from-target-alerts/222 "2024-08-08T14:18:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mtorres239](https://avatars.discourse-cdn.com/v4/letter/m/35a633/32.png) [@mtorres239](https://community.netbeez.net/u/mtorres239)\
**Post date:** [August 8, 2024, 2:18pm UTC](https://community.netbeez.net/t/exempt-specific-nodes-from-target-alerts/222/1 "2024-08-08T14:18:40Z")

</div>

Hi all,  
We have started the PagerDuty integration. We have a few agents that often end up in problem areas for troubleshooting.

My question is: Is there a way to exempt a specific agent or ‘pause’ it’s alerting without stopping the testing/targets?

TIA!  
/mt

---

<div class="post-metadata">

**Author:** ![panickos](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.netbeez.net/panickos/32/8_2.png) [@panickos](https://community.netbeez.net/u/panickos)\
**Post date:** [August 12, 2024, 9:17pm UTC](https://community.netbeez.net/t/exempt-specific-nodes-from-target-alerts/222/2 "2024-08-12T21:17:31Z")

</div>

I’ve done some research on how to better handle routing of events within Pagerduty and it looks like what you asking for may be supported using Event Orchestration.

That option is available in the Automation → [Event Orchestration](https://support.pagerduty.com/main/docs/event-orchestration) section:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/netbeez/original/1X/9f10eb38b49760496207a8fd50b163adbe9e9778.png)

I tried adding a filter to Agent incident based on agent names like so by means of a Service Route:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/netbeez/original/1X/16abd5748c43821416091d84c5c92cfc6531ce70.png)

Now depending on your specific use-case you may want to implement different rules but the general idea is there. If you need any help getting details on the schema of certain events let me know.

Please note that the Integration Key for the Automation part is different that the key provided on the “Service” level.

…and welcome to our community!