Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/reference/filebeat/filebeat-input-journald.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,9 @@ applies_to:
[`journald`](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) is a system service that collects and stores logging data. The `journald` input reads this log data and the metadata associated with it. To read this log data Filebeat calls `journalctl` to read from the journal, therefore Filebeat needs permission to execute `journalctl`.

:::{warning}
The Wolfi-based Docker image does not contain the `journalctl` binary and the `journald` input type cannot be used with it.
The Wolfi-based Docker image does not contain the `journalctl` binary.

{applies_to}`stack: ga 9.3.0` To use the `journald` input type with Wolfi images, you must configure the [`chroot`](#filebeat-input-journald-chroot) option to use the host's `journalctl` binary.
:::

:::{important}
Expand All @@ -32,8 +34,6 @@ either:

:::

If the `journalctl` process exits unexpectedly the journald input will terminate with an error and Filebeat will need to be restarted to start reading from the journal again.

The simplest configuration example is one that reads all logs from the default journal.

```yaml
Expand Down
Loading