diff options
author | Costa Tsaousis <costa@netdata.cloud> | 2023-10-18 19:42:59 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-10-18 19:42:59 +0300 |
commit | d3ad8eb63b50c9d767434af08d218d7d35667d33 (patch) | |
tree | 7db6df637ca97be1fca69e91efeeaa444e18de3f /collectors/systemd-journal.plugin | |
parent | 1d43482291aaee4fc20da7f660c4f7fd4f23a27f (diff) |
Update passive_journal_centralization_guide_self_signed_certs.md
Diffstat (limited to 'collectors/systemd-journal.plugin')
-rw-r--r-- | collectors/systemd-journal.plugin/passive_journal_centralization_guide_self_signed_certs.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/collectors/systemd-journal.plugin/passive_journal_centralization_guide_self_signed_certs.md b/collectors/systemd-journal.plugin/passive_journal_centralization_guide_self_signed_certs.md index 18c47588f3..9dcfa6dec4 100644 --- a/collectors/systemd-journal.plugin/passive_journal_centralization_guide_self_signed_certs.md +++ b/collectors/systemd-journal.plugin/passive_journal_centralization_guide_self_signed_certs.md @@ -2,7 +2,7 @@ This page will guide you through creating a **passive** journal centralization setup using **self-signed certificates** for encryption and authorization. -Once you centralize your infrastructure logs to a server, Netdata will automatically detects all the logs from all servers and organize them in sources. With the setup described in this document, Netdata will automatically name all remote sources using the names of the clients, as they are described at their certificates. +Once you centralize your infrastructure logs to a server, Netdata will automatically detect all the logs from all servers and organize them in sources. With the setup described in this document, Netdata will automatically name all remote sources using the names of the clients, as they are described at their certificates. A **passive** journal server waits for clients to push their metrics to it, so in this setup we will: |