From 9d2b1ea83678293318dac5a62d6940a10773927a Mon Sep 17 00:00:00 2001
From: Oliver Harrison <87360652+ollieharDD@users.noreply.github.com>
Date: Wed, 6 Mar 2024 11:28:46 +0100
Subject: [PATCH] Update README.md

Motivation:
- Working on a customer case, we discovered that the following prevented log collection:
```
include_units:
  - *
```

Supporting Documentation:
- https://github.com/DataDog/datadog-agent/blob/7.50.x/pkg/logs/tailers/journald/tailer.go#L116-L126
---
 journald/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/journald/README.md b/journald/README.md
index a71016ae0cdea..38acf5a674eff 100644
--- a/journald/README.md
+++ b/journald/README.md
@@ -85,7 +85,7 @@ If your journal is located elsewhere, add a `path` parameter with the correspond
 
 You can filter specific _system-level_ units by using these parameters:
 
-- `include_units`: Includes all system-level units specified.
+- `include_units`: Includes all system-level units specified. To collect
 - `exclude_units`: Excludes all system-level units specified.
 
 
@@ -105,7 +105,7 @@ In Datadog Agent version `7.37.0`+, you can filter _user-level_ units by using t
 - `include_user_units`: Includes all user-level units specified.
 - `exclude_user_units`: Excludes all user-level units specified.
 
-**Note**: Use the `*` wildcard in `exclude_units` or `exclude_user_units` to specify a particular Journald log.
+**Note**: Use the `*` wildcard in `exclude_units` or `exclude_user_units` to specify a particular Journald log. Further note that `*` will not work with `include_units`, by default if no units for both System and User, and no matches are defined, all journal logs will be collected.
 
 Example: