# Exclude Process unavailable alerts from old pods

**URL:** <https://community.dynatrace.com/t/exclude-process-unavailable-alerts-from-old-pods/48255>\
**Category:** Open Q&A\
**Tags:** openshift, problems-classic\
**Created:** [October 10, 2024, 1:06pm UTC](https://community.dynatrace.com/t/exclude-process-unavailable-alerts-from-old-pods/48255 "2024-10-10T13:06:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![erh\_inetum](https://avatars.discourse-cdn.com/v4/letter/e/48db29/32.png) [@erh\_inetum](https://community.dynatrace.com/u/erh_inetum)\
**Post date:** [October 10, 2024, 1:06pm UTC](https://community.dynatrace.com/t/exclude-process-unavailable-alerts-from-old-pods/48255/1 "2024-10-10T13:06:58Z")

</div>

Hi,

We are getting this kind of problems:

 ![erh_inetum_0-1728564393450.png](https://global.discourse-cdn.com/dynatrace/original/2X/0/019e1d01fd7aee3a9af7397f2f2531d12b66827a.png)

But &nbsp;it’s not really an issue.

When a new deployment is done, current active pods are stopped and new pods are started. So the name of the processes change and Dynatrace detects as that the process is stopped but it’s not true because the same one is started in another pod:

 ![erh_inetum_2-1728564883109.png](https://global.discourse-cdn.com/dynatrace/original/2X/4/44ee97a0e6920df4fff75ba350cb4bf93a1696b8.png)

We want to monitor the availability of the process group, which is the same for all processes. But we don´t want to receive this kind of alerts.

Is any way to get that?

Thanks in advance.

Regards,

Elena.

---

<div class="post-metadata">

**Author:** ![StrangerThing](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/strangerthing/32/12182_2.png) [@StrangerThing](https://community.dynatrace.com/u/StrangerThing)\
**Post date:** [October 10, 2024, 5:43pm UTC](https://community.dynatrace.com/t/exclude-process-unavailable-alerts-from-old-pods/48255/2 "2024-10-10T17:43:23Z")

</div>

You could maybe use this setting instead of alerting if any process becomes unavailable.

 ![StrangerThing_0-1728582194163.png](https://global.discourse-cdn.com/dynatrace/original/2X/7/75167b7937063ededb0176e9ebdfa0118d0c6b95.png)

---

<div class="post-metadata">

**Author:** ![erh\_inetum](https://avatars.discourse-cdn.com/v4/letter/e/48db29/32.png) [@erh\_inetum](https://community.dynatrace.com/u/erh_inetum)\
**Post date:** [October 11, 2024, 4:08am UTC](https://community.dynatrace.com/t/exclude-process-unavailable-alerts-from-old-pods/48255/3 "2024-10-11T04:08:43Z")

</div>

Hi,

Thanks a lot for your answer.

We have enabled this configuration at process group level. And we want to receiving and alert when the process it’s unavailable. But not when a pod is stopping a pod and a new one is starting because it’s a controlled situation.

Is it possible to get that? Any ideas?  
Thanks again.  
Regards,  
Elena.

---

<div class="post-metadata">

**Author:** ![KIKON](https://avatars.discourse-cdn.com/v4/letter/k/f05b48/32.png) [@KIKON](https://community.dynatrace.com/u/KIKON)\
**Post date:** [October 11, 2024, 6:36am UTC](https://community.dynatrace.com/t/exclude-process-unavailable-alerts-from-old-pods/48255/4 "2024-10-11T06:36:54Z")

</div>

Two options.

1. deactivate process unavailable and create a similar custom alert with other priority, informational for example.

2. Launch maintenance windows for supress problems only in lapse period of deployment.

---

<div class="post-metadata">

**Author:** ![erh\_inetum](https://avatars.discourse-cdn.com/v4/letter/e/48db29/32.png) [@erh\_inetum](https://community.dynatrace.com/u/erh_inetum)\
**Post date:** [October 14, 2024, 8:16am UTC](https://community.dynatrace.com/t/exclude-process-unavailable-alerts-from-old-pods/48255/5 "2024-10-14T08:16:37Z")

</div>

Hi Enrique,

The option 2 proposed works.

Thanks you so much!

Regards,

Elena.