# Child node logs are unavailable on Parent when Child is offline

**URL:** <https://community.netdata.cloud/t/child-node-logs-are-unavailable-on-parent-when-child-is-offline/6118>\
**Category:** Help\
**Tags:** agent, streaming\
**Created:** [December 20, 2024, 10:11pm UTC](https://community.netdata.cloud/t/child-node-logs-are-unavailable-on-parent-when-child-is-offline/6118 "2024-12-20T22:11:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![corymosiman12](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/corymosiman12/32/3710_2.png) [@corymosiman12](https://community.netdata.cloud/u/corymosiman12)\
**Post date:** [December 20, 2024, 10:11pm UTC](https://community.netdata.cloud/t/child-node-logs-are-unavailable-on-parent-when-child-is-offline/6118/1 "2024-12-20T22:11:29Z")

</div>

## Problem/Question

Child node logs are unavailable on Parent when Child is offline.

I have successfully configured multiple child nodes streaming to a single parent. It is functioning as expected. Clicking on the “Logs” tab in Netdata, I am able to see in realtime the systemd logs of the parent and all children. This is awesome.

However, if I take a child offline and refresh the “Logs” tab, the child nodes logs are no longer available for viewing. A major use case (for us) in streaming the logs from child → parent is to assist in root cause analysis of child node failures.

## Relevant docs you followed/actions you took to solve the issue

- [Configure Netdata Parents to centralize metrics | Learn Netdata](https://learn.netdata.cloud/docs/observability-centralization-points/metrics-centralization-points/)
- [Systemd Journal Logs | Learn Netdata](https://learn.netdata.cloud/docs/logs/systemd-journal-logs)

## Environment/Browser/Agent’s version etc

- Parent: v1.45.5
- Children: v1.47.5

## What I expected to happen

When the child node goes offline, I am still able to see the historical systemd logs for the offline child via the parent node dashboard.

---

<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:** [December 21, 2024, 12:53pm UTC](https://community.netdata.cloud/t/child-node-logs-are-unavailable-on-parent-when-child-is-offline/6118/2 "2024-12-21T12:53:27Z")

</div>

> [@corymosiman12](#):
>
> However, if I take a child offline and refresh the “Logs” tab, the child nodes logs are no longer available for viewing.

Hi, @corymosiman12. That is how it works - You access child node logs through the parent node. Child nodes do not directly stream or send their host logs to the parent.

---

<div class="post-metadata">

**Author:** ![ralphm](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ralphm/32/1934_2.png) [@ralphm](https://community.netdata.cloud/u/ralphm)\
**Post date:** [December 22, 2024, 10:45am UTC](https://community.netdata.cloud/t/child-node-logs-are-unavailable-on-parent-when-child-is-offline/6118/3 "2024-12-22T10:45:37Z")

</div>

To add to this, if you want to have logs available in another location, for example for ephemeral nodes, you can follow this guide: [Passive journal centralization with encryption using self-signed certificates | Learn Netdata](https://learn.netdata.cloud/docs/observability-centralization-points/logs-centralization-points-with-systemd-journald/passive-journal-centralization-with-encryption-using-self-signed-certificates).