From e4b2d6d8c0949fc4bedc2c42a76751d0d251a281 Mon Sep 17 00:00:00 2001 From: ebner Date: Thu, 19 Mar 2026 14:31:53 +0100 Subject: [PATCH] Update docs/admin-guide/configuration/monitoring/central_logging_elastic.md --- .../configuration/monitoring/central_logging_elastic.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin-guide/configuration/monitoring/central_logging_elastic.md b/docs/admin-guide/configuration/monitoring/central_logging_elastic.md index 2578eb7f..62a67fe1 100644 --- a/docs/admin-guide/configuration/monitoring/central_logging_elastic.md +++ b/docs/admin-guide/configuration/monitoring/central_logging_elastic.md @@ -31,7 +31,7 @@ Replace the space name as well as the space_api_key according to your setup. Notice that `space` contains the `name` without the `input_` prefix, while `space_api_key` contains a `:`-separated value: * the first part corresponds to the `id` of the space, * the second part corresponds to the `api_key`. -* The resulting string `"${space_id}:${space_api_key}"` **should be encrypted** with [eyaml](../../puppet/hiera) +* The resulting string `"${space_id}:${space_api_key}"` **should be encrypted** with [eyaml](../../puppet/hiera/#secrets) By default __all__ journald logs are shipped to the central Elastic instance. If you want to __limit__ the logs to specific units, the units can be specified as follows: