From 25a98fc3c3c652ed6201341901e827556c95cd9f Mon Sep 17 00:00:00 2001 From: May Lee Date: Fri, 21 Nov 2025 11:23:43 -0500 Subject: [PATCH 1/2] add custom option --- .../observability_pipelines/source_settings/http_client.en.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/layouts/shortcodes/observability_pipelines/source_settings/http_client.en.md b/layouts/shortcodes/observability_pipelines/source_settings/http_client.en.md index 9cb121b8c9a5e..b2abe3a84453b 100644 --- a/layouts/shortcodes/observability_pipelines/source_settings/http_client.en.md +++ b/layouts/shortcodes/observability_pipelines/source_settings/http_client.en.md @@ -1,6 +1,7 @@ To configure your HTTP/S Client source: -1. Select your authorization strategy. +1. Select your authorization strategy (**None**,**Basic**, **Bearer**, or **Custom**). + - For the **Custom** option, the value is added to the headers as `Authorization: `. 2. Select the decoder you want to use on the HTTP messages. Logs pulled from the HTTP source must be in this format. 3. Optionally, toggle the switch to enable TLS. If you enable TLS, the following certificate and key files are required.
**Note**: All file paths are made relative to the configuration data directory, which is `/var/lib/observability-pipelines-worker/config/` by default. See [Advanced Configurations][10172] for more information. The file must be owned by the `observability-pipelines-worker group` and `observability-pipelines-worker` user, or at least readable by the group or user. - `Server Certificate Path`: The path to the certificate file that has been signed by your Certificate Authority (CA) Root File in DER or PEM (X.509) format. From b4abf04954046cf9dcfdc7872c85aa940ee861a4 Mon Sep 17 00:00:00 2001 From: May Lee Date: Fri, 21 Nov 2025 11:31:00 -0500 Subject: [PATCH 2/2] small edit --- .../observability_pipelines/source_settings/http_client.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/layouts/shortcodes/observability_pipelines/source_settings/http_client.en.md b/layouts/shortcodes/observability_pipelines/source_settings/http_client.en.md index b2abe3a84453b..8ebe74c9f53d1 100644 --- a/layouts/shortcodes/observability_pipelines/source_settings/http_client.en.md +++ b/layouts/shortcodes/observability_pipelines/source_settings/http_client.en.md @@ -1,7 +1,7 @@ To configure your HTTP/S Client source: 1. Select your authorization strategy (**None**,**Basic**, **Bearer**, or **Custom**). - - For the **Custom** option, the value is added to the headers as `Authorization: `. + - For **Custom**, the value is added to the headers as `Authorization: `. 2. Select the decoder you want to use on the HTTP messages. Logs pulled from the HTTP source must be in this format. 3. Optionally, toggle the switch to enable TLS. If you enable TLS, the following certificate and key files are required.
**Note**: All file paths are made relative to the configuration data directory, which is `/var/lib/observability-pipelines-worker/config/` by default. See [Advanced Configurations][10172] for more information. The file must be owned by the `observability-pipelines-worker group` and `observability-pipelines-worker` user, or at least readable by the group or user. - `Server Certificate Path`: The path to the certificate file that has been signed by your Certificate Authority (CA) Root File in DER or PEM (X.509) format.