# Why pod restart doesn't alert dynatrace

**URL:** <https://community.dynatrace.com/t/why-pod-restart-doesnt-alert-dynatrace/22114>\
**Category:** Alerting\
**Tags:** problem-detection, kubernetes, problems-classic\
**Created:** [September 30, 2019, 9:05am UTC](https://community.dynatrace.com/t/why-pod-restart-doesnt-alert-dynatrace/22114 "2019-09-30T09:05:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gilles\_djimi-ex](https://avatars.discourse-cdn.com/v4/letter/g/ad7895/32.png) [@gilles\_djimi-ex](https://community.dynatrace.com/u/gilles_djimi-ex)\
**Post date:** [September 30, 2019, 9:05am UTC](https://community.dynatrace.com/t/why-pod-restart-doesnt-alert-dynatrace/22114/1 "2019-09-30T09:05:05Z")

</div>

We running Dynatrace on a gke cluster and when pod restarts it is not shown in Dynatrace, even worst, it shows the old pod as unmonitored.

Hence here is my question, how can I make an alerte on Dynatrace on every pod restart. Just for information I’am running Dynatrace on managed version.

Thanks

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [September 30, 2019, 9:29am UTC](https://community.dynatrace.com/t/why-pod-restart-doesnt-alert-dynatrace/22114/2 "2019-09-30T09:29:15Z")

</div>

It’s because as you don’t restart pod but destroy instance and create new one (new ID assigned to OneAgent). As I understand you are using not full stack monitoring but application only monitoring?

Sebastian

---

<div class="post-metadata">

**Author:** ![gilles\_djimi-ex](https://avatars.discourse-cdn.com/v4/letter/g/ad7895/32.png) [@gilles\_djimi-ex](https://community.dynatrace.com/u/gilles_djimi-ex)\
**Post date:** [October 3, 2019, 2:55pm UTC](https://community.dynatrace.com/t/why-pod-restart-doesnt-alert-dynatrace/22114/3 "2019-10-03T14:55:26Z")

</div>

No I’am using the fullstack monitoring and we are not destroying instances, it just that pod restart doesn’t show on dynatrace properly it display a message that a pod is not monitored or that the signal was lost.

If I take an example: Let’s say we have 3 runing process, and all the 3 are restarted, then all the new pod will be display in dynatrace while the old one are marked as unmonitored or “signal lost” tagged.

 ![22062-capture-decran-29.png](https://global.discourse-cdn.com/dynatrace/original/2X/f/f1403f4cea54db53c6c96d96359e0cbc914bc8d7.png)

For example in the above image we can see that the old pod are seen as unmonitored or have a “lost signal” tag.

My question is how can we properly configure Dynatrace to properly show the pod information. Or is this normal and only used to see old pod metrics

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [October 3, 2019, 7:05pm UTC](https://community.dynatrace.com/t/why-pod-restart-doesnt-alert-dynatrace/22114/4 "2019-10-03T19:05:15Z")

</div>

This is regular behaviour.

Sebastian

---

<div class="post-metadata">

**Author:** ![Dant3](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dant3/32/159_2.png) [@Dant3](https://community.dynatrace.com/u/Dant3)\
**Post date:** [October 3, 2019, 10:08pm UTC](https://community.dynatrace.com/t/why-pod-restart-doesnt-alert-dynatrace/22114/5 "2019-10-03T22:08:10Z")

</div>

We had the same inquery. We notice that the pod would die before a new one showup.

We configure a minimun of running process for that PG and a minimun of pods in OCP. So in the case of a new pod we get an alert that the PG is lower than it should be.

---

<div class="post-metadata">

**Author:** ![gilles\_djimi-ex](https://avatars.discourse-cdn.com/v4/letter/g/ad7895/32.png) [@gilles\_djimi-ex](https://community.dynatrace.com/u/gilles_djimi-ex)\
**Post date:** [October 4, 2019, 10:22am UTC](https://community.dynatrace.com/t/why-pod-restart-doesnt-alert-dynatrace/22114/6 "2019-10-04T10:22:56Z")

</div>

Can we change the normal behaviour so that old pod doesn’t show up as unmonitored or tagged with “lost signal” ? Additionnaly is that possible to make Dynatrace makes an alert to any pod restart.
