# Non-persistent nodes

**URL:** <https://community.netdata.cloud/t/non-persistent-nodes/4480>\
**Category:** Help\
**Created:** [August 1, 2023, 6:20pm UTC](https://community.netdata.cloud/t/non-persistent-nodes/4480 "2023-08-01T18:20:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![derm](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/derm/32/3041_2.png) [@derm](https://community.netdata.cloud/u/derm)\
**Post date:** [August 1, 2023, 6:20pm UTC](https://community.netdata.cloud/t/non-persistent-nodes/4480/1 "2023-08-01T18:20:57Z")

</div>

Is there any support for non-persistent nodes? I’d like to monior a fleet of thin clients which do not have persistent disks (all changes are lost upon reboot). I’m able to run the kickstarter script upon bootup, but every time it is run, a new entry for that node is created. Is there a good way to link it to an existing node so it doesn’t clutter up the dashboard? Alternatively, can nodes be deleted automatically once they lose connection for a certain amount of time?

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [August 1, 2023, 8:27pm UTC](https://community.netdata.cloud/t/non-persistent-nodes/4480/2 "2023-08-01T20:27:58Z")

</div>

> Alternatively, can nodes be deleted automatically once they lose connection for a certain amount of time?

Hey, @derm. I am not sure but I think it is supposed to work that way when

```auto
# netdata.conf
[health]
    is ephemeral = yes

```

I will ask/test this.

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [August 2, 2023, 2:42pm UTC](https://community.netdata.cloud/t/non-persistent-nodes/4480/3 "2023-08-02T14:42:54Z")

</div>

Ok, I checked - that option doesn’t do. I don’t think there is a way to remove/cleanup ephemeral hosts if using dbengine mem mode.
