# How to make a containers recycle looks clean?

**URL:** <https://community.dynatrace.com/t/how-to-make-a-containers-recycle-looks-clean/20109>\
**Category:** Container platforms\
**Tags:** docker\
**Created:** [March 25, 2019, 2:39am UTC](https://community.dynatrace.com/t/how-to-make-a-containers-recycle-looks-clean/20109 "2019-03-25T02:39:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![waikeat\_chan](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/waikeat_chan/32/33405_2.png) [@waikeat\_chan](https://community.dynatrace.com/u/waikeat_chan)\
**Post date:** [March 25, 2019, 2:39am UTC](https://community.dynatrace.com/t/how-to-make-a-containers-recycle-looks-clean/20109/1 "2019-03-25T02:39:13Z")

</div>

For the containerized service, everything looks fine (looks fine in the sense that, every time the underlying docker is recycle, I didn’t see any gap or broken pieces in the metric graph in service layer)

 ![20099-old-containers-unmonitored.png](https://global.discourse-cdn.com/dynatrace/original/2X/1/17b7e41360a92d85460fd30b5017cf75a180b6c1.png)

However, in host layer. The old containers would always goes into the state of ‘unmonitored’.

For example, as this screenshot shown, api-private-gateway would always get its name increment by one each time it recycle. Right now, api-private-gateway-64-\* is running, is there anyway I can make the containers before 64 disappear? (or, if they are gonna still be there can their state change from ‘unmonitored’ to something more…meaningful per se?)

Best Regards,

Wai Keat

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [April 16, 2020, 2:38pm UTC](https://community.dynatrace.com/t/how-to-make-a-containers-recycle-looks-clean/20109/2 "2020-04-16T14:38:27Z")

</div>

There is a new method where you need to pass an event within 60mins of the recycle which will then keep you from being alerted when a host is being spun down in cloud environments. You can read more about it here: [Dynatrace Blog | Dynatrace news](https://www.dynatrace.com/news/blog/new-event-type-helps-avoid-unnecessary-alerts-for-planned-host-downscaling/)

---

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [April 16, 2020, 3:06pm UTC](https://community.dynatrace.com/t/how-to-make-a-containers-recycle-looks-clean/20109/3 "2020-04-16T15:06:20Z")

</div>

That’s neat but doesn’t really help addressing the “unmonitored” PaaS hosts spam for terminated containers/pods in an application-only monitoring scenario (= oneagent is manually deployed into the container).

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [April 16, 2020, 3:14pm UTC](https://community.dynatrace.com/t/how-to-make-a-containers-recycle-looks-clean/20109/4 "2020-04-16T15:14:20Z")

</div>

Correct, and until Dynatrace has a solution for these scenarios.