summaryrefslogtreecommitdiffstats
path: root/collectors
diff options
context:
space:
mode:
authorCosta Tsaousis <costa@netdata.cloud>2023-10-07 13:43:04 +0300
committerGitHub <noreply@github.com>2023-10-07 13:43:04 +0300
commit3e7c4891518d1628ff988ee756efef7ae36f144d (patch)
tree6c40cbadf31debf2a430a7e91253abc1eefebe1b /collectors
parenta7c1e6bd2b235c2e962ecc0e8a4c76210a997fe6 (diff)
Update README.md
Diffstat (limited to 'collectors')
-rw-r--r--collectors/systemd-journal.plugin/README.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/collectors/systemd-journal.plugin/README.md b/collectors/systemd-journal.plugin/README.md
index bd1bdaeb4b..aa221467f7 100644
--- a/collectors/systemd-journal.plugin/README.md
+++ b/collectors/systemd-journal.plugin/README.md
@@ -270,7 +270,8 @@ even if every single message has unique fields and values.
When you send `systemd` journal logs to Loki, even if you use the `relabel_rules` argument to
`loki.source.journal` with a JSON format, you need to specify which of the fields from journald
-you want inherited by Loki. This means you loose all the flexibility `systemd` journal provides:
+you want inherited by Loki. This means you need to know the most important fields beforehand.
+At the same time you loose all the flexibility `systemd` journal provides:
**indexing on all fields and all their values**.
Loki generally assumes that all logs are like a table. All entries in a stream share the same