diff options
| author | Costa Tsaousis <costa@netdata.cloud> | 2023-10-15 20:58:59 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-15 20:58:59 +0300 |
| commit | 6d42158e3f07dd29a8c31bb7f62d89779d922a0c (patch) | |
| tree | 10d585a99ee28fbdbef54d23aaa5e56900fc843b | |
| parent | a7dc81d661656ab3318bbdd29b79475e3ffaae0e (diff) | |
Update README.md
| -rw-r--r-- | collectors/systemd-journal.plugin/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/collectors/systemd-journal.plugin/README.md b/collectors/systemd-journal.plugin/README.md index 2ab2c33b01..771df04bbf 100644 --- a/collectors/systemd-journal.plugin/README.md +++ b/collectors/systemd-journal.plugin/README.md @@ -354,7 +354,7 @@ fields. But journald does exactly the opposite. Each log entry is unique and may So, Loki and `systemd-journal` are good for different use cases. `systemd-journal` already runs in your systems. You use it today. It is there inside all your systems -collecting the system and app~~~~lications logs. And for its use case, it has advantages over other +collecting the system and applications logs. And for its use case, it has advantages over other centralization solutions. So, why not use it? ### Is it worth to build a `systemd` logs centralization server? |