From b9ef6a705f000ad7dd9e61ec812eb7cc2f981cae Mon Sep 17 00:00:00 2001 From: May Lee Date: Thu, 20 Aug 2026 15:43:13 -0400 Subject: [PATCH 1/3] updates --- .../observability_pipelines/destinations/datadog_archives.md | 2 +- .../amazon_s3/connect_s3_to_datadog_log_archives.en.md | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/hugo/content/en/observability_pipelines/destinations/datadog_archives.md b/hugo/content/en/observability_pipelines/destinations/datadog_archives.md index 7bdf018ab90..f4aed7176e4 100644 --- a/hugo/content/en/observability_pipelines/destinations/datadog_archives.md +++ b/hugo/content/en/observability_pipelines/destinations/datadog_archives.md @@ -95,7 +95,7 @@ After you select the Datadog Archives destination in the pipeline UI: 1. Enter the AWS region the S3 bucket is in. 1. Enter the key prefix. - Prefixes are useful for partitioning objects. For example, you can use a prefix as an object key to store objects under a particular directory. If using a prefix for this purpose, it must end in `/` to act as a directory path; a trailing `/` is not automatically added. - - See [template syntax][8] if you want to route logs to different object keys based on specific fields in your logs. + - See [template syntax][8] if you want to route logs to different object keys based on specific fields in your logs. This **Prefix** field is the only place to configure template syntax for this destination; the path you optionally enter when [configuring Log Archives](#configure-log-archives) must be a static string. - **Note**: Datadog recommends that you start your prefixes with the directory name and without a lead slash (`/`). For example, `app-logs/` or `service-logs/`. 1. Select the storage class for your S3 bucket in the {{< ui >}}Storage Class{{< /ui >}} dropdown menu. If you are going to archive and rehydrate your logs: - **Note**: Rehydration only supports the following [storage classes][9]: diff --git a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/amazon_s3/connect_s3_to_datadog_log_archives.en.md b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/amazon_s3/connect_s3_to_datadog_log_archives.en.md index 52fa6dd4dc8..02758f5e63c 100644 --- a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/amazon_s3/connect_s3_to_datadog_log_archives.en.md +++ b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/amazon_s3/connect_s3_to_datadog_log_archives.en.md @@ -8,6 +8,7 @@ 1. Select the AWS account that your bucket is in. 1. Enter the name of the S3 bucket. 1. Optionally, enter a path. + - **Note**: This path must be a static string. It does not support template syntax (for example, `{{ tag_name }}`). To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the Datadog Archives destination for your pipeline][204] instead. 1. Check the confirmation statement. 1. Optionally, add tags and define the maximum scan size for rehydration. See [Advanced settings][202] for more information. 1. Click **Save**. @@ -16,4 +17,5 @@ See the [Log Archives documentation][203] for additional information. [201]: https://app.datadoghq.com/logs/pipelines/log-forwarding [202]: /logs/log_configuration/archives/?tab=awss3#advanced-settings -[203]: /logs/log_configuration/archives \ No newline at end of file +[203]: /logs/log_configuration/archives +[204]: /observability_pipelines/destinations/datadog_archives/#set-up-the-destination-for-your-pipeline \ No newline at end of file From 0e29d2a4994240f9daf4232a2513978fb47778fa Mon Sep 17 00:00:00 2001 From: May Lee Date: Thu, 20 Aug 2026 15:58:38 -0400 Subject: [PATCH 2/3] update az and gcp --- .../en/observability_pipelines/destinations/azure_storage.md | 2 +- .../destinations/google_cloud_storage.md | 2 +- .../configure_log_archive/azure_storage/instructions.en.md | 4 +++- .../google_cloud_storage/instructions.en.md | 4 +++- 4 files changed, 8 insertions(+), 4 deletions(-) diff --git a/hugo/content/en/observability_pipelines/destinations/azure_storage.md b/hugo/content/en/observability_pipelines/destinations/azure_storage.md index c4580a6e8f8..6a47bcb7306 100644 --- a/hugo/content/en/observability_pipelines/destinations/azure_storage.md +++ b/hugo/content/en/observability_pipelines/destinations/azure_storage.md @@ -41,7 +41,7 @@ After you select the Azure Storage destination in the pipeline UI: Enter a prefix that you want to apply to all key objects. - Prefixes are useful for partitioning objects. For example, you can use a prefix as an object key to store objects under a particular directory. If using a prefix for this purpose, it must end in `/` to act as a directory path; a trailing `/` is not automatically added. -- See [template syntax][6] if you want to route logs to different object keys based on specific fields in your logs. +- See [template syntax][6] if you want to route logs to different object keys based on specific fields in your logs. This **Prefix** field is the only place to configure template syntax for this destination; the path you optionally enter when [configuring Log Archives](#configure-log-archives) must be a static string. - **Note**: Datadog recommends that you start your prefixes with the directory name and without a lead slash (`/`). For example, `app-logs/` or `service-logs/`. #### Buffering diff --git a/hugo/content/en/observability_pipelines/destinations/google_cloud_storage.md b/hugo/content/en/observability_pipelines/destinations/google_cloud_storage.md index d0118f4a396..b18f778ea33 100644 --- a/hugo/content/en/observability_pipelines/destinations/google_cloud_storage.md +++ b/hugo/content/en/observability_pipelines/destinations/google_cloud_storage.md @@ -47,7 +47,7 @@ After you select the Google Cloud Storage destination in the pipeline UI: Enter a prefix that you want to apply to all key objects. - Prefixes are useful for partitioning objects. For example, you can use a prefix as an object key to store objects under a particular directory. If using a prefix for this purpose, it must end in `/` to act as a directory path; a trailing `/` is not automatically added. -- See [template syntax][7] if you want to route logs to different object keys based on specific fields in your logs. +- See [template syntax][7] if you want to route logs to different object keys based on specific fields in your logs. This **Prefix** field is the only place to configure template syntax for this destination; the path you optionally enter when [configuring Log Archives](#configure-log-archives) must be a static string. - **Note**: Datadog recommends that you start your prefixes with the directory name and without a lead slash (`/`). For example, `app-logs/` or `service-logs/`. #### Metadata diff --git a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/azure_storage/instructions.en.md b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/azure_storage/instructions.en.md index f72fab4bc5f..68eb4f58ac5 100644 --- a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/azure_storage/instructions.en.md +++ b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/azure_storage/instructions.en.md @@ -31,6 +31,7 @@ Create an [Azure storage account][9051] if you don't already have one. 1. Enter the name of the storage account. 1. Enter the name of the container you created earlier. 1. Optionally, enter a path. + - **Note**: This path must be a static string. It does not support template syntax (for example, `{{ tag_name }}`). To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the Azure Storage destination for your pipeline][9057] instead. 1. Optionally, set permissions, add tags, and define the maximum scan size for rehydration. See [Advanced settings][9055] for more information. 1. Click **Save**. @@ -41,4 +42,5 @@ See the [Log Archives documentation][9056] for additional information. [9053]: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-immutability-policies-manage [9054]: https://app.datadoghq.com/logs/pipelines/log-forwarding [9055]: /logs/log_configuration/archives/?tab=awss3#advanced-settings -[9056]: /logs/log_configuration/archives \ No newline at end of file +[9056]: /logs/log_configuration/archives +[9057]: /observability_pipelines/destinations/azure_storage/#set-up-the-destination-for-your-pipeline \ No newline at end of file diff --git a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/google_cloud_storage/instructions.en.md b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/google_cloud_storage/instructions.en.md index c4b7ae99331..ab819134014 100644 --- a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/google_cloud_storage/instructions.en.md +++ b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/google_cloud_storage/instructions.en.md @@ -25,6 +25,7 @@ 1. Select the project. 1. Enter the name of the storage bucket you created earlier. 1. Optionally, enter a path. + - **Note**: This path must be a static string. It does not support template syntax (for example, `{{ tag_name }}`). To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the Google Cloud Storage destination for your pipeline][9097] instead. 1. Optionally, set permissions, add tags, and define the maximum scan size for rehydration. See [Advanced settings][9095] for more information. 1. Click **Save**. @@ -35,4 +36,5 @@ See the [Log Archives documentation][9096] for additional information. [9093]: https://cloud.google.com/iam/docs/keys-create-delete#creating [9094]: https://app.datadoghq.com/logs/pipelines/log-forwarding [9095]: /logs/log_configuration/archives/?tab=awss3#advanced-settings -[9096]: /logs/log_configuration/archives \ No newline at end of file +[9096]: /logs/log_configuration/archives +[9097]: /observability_pipelines/destinations/google_cloud_storage/#set-up-the-destinations \ No newline at end of file From c513cd5d53927f81f5e9a8d5eb17c73e0e636989 Mon Sep 17 00:00:00 2001 From: May Lee Date: Fri, 21 Aug 2026 15:34:10 -0400 Subject: [PATCH 3/3] updates --- .../en/observability_pipelines/destinations/azure_storage.md | 1 + .../observability_pipelines/destinations/datadog_archives.md | 1 + .../destinations/google_cloud_storage.md | 1 + .../amazon_s3/connect_s3_to_datadog_log_archives.en.md | 4 +--- .../configure_log_archive/azure_storage/instructions.en.md | 4 +--- .../google_cloud_storage/instructions.en.md | 4 +--- 6 files changed, 6 insertions(+), 9 deletions(-) diff --git a/hugo/content/en/observability_pipelines/destinations/azure_storage.md b/hugo/content/en/observability_pipelines/destinations/azure_storage.md index 0b5ce050e9e..c0648ee1106 100644 --- a/hugo/content/en/observability_pipelines/destinations/azure_storage.md +++ b/hugo/content/en/observability_pipelines/destinations/azure_storage.md @@ -53,6 +53,7 @@ Create an [Azure storage account][13] if you don't already have one. 1. Enter the name of the storage account. 1. Enter the name of the container you created earlier. 1. Optionally, enter a path. + - **Note**: This path must be a static string. It does not support template syntax, such as `{{ tag_name }}`. To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline) instead. 1. Optionally, set permissions, add tags, and define the maximum scan size for rehydration. See [Advanced settings][17] for more information. 1. Click **Save**. diff --git a/hugo/content/en/observability_pipelines/destinations/datadog_archives.md b/hugo/content/en/observability_pipelines/destinations/datadog_archives.md index ca7a7bd3df1..792c0cb83c9 100644 --- a/hugo/content/en/observability_pipelines/destinations/datadog_archives.md +++ b/hugo/content/en/observability_pipelines/destinations/datadog_archives.md @@ -94,6 +94,7 @@ If you already have Datadog Log Archives configured, skip to [Set up the destina 1. Select the AWS account that your bucket is in. 1. Enter the name of the S3 bucket. 1. Optionally, enter a path. + - **Note**: This path must be a static string. It does not support template syntax, such as `{{ tag_name }}`. To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline) instead. 1. Check the confirmation statement. 1. Optionally, add tags and define the maximum scan size for rehydration. See [Advanced settings][18] for more information. 1. Click **Save**. diff --git a/hugo/content/en/observability_pipelines/destinations/google_cloud_storage.md b/hugo/content/en/observability_pipelines/destinations/google_cloud_storage.md index aec6156cbfe..aafaa1806c4 100644 --- a/hugo/content/en/observability_pipelines/destinations/google_cloud_storage.md +++ b/hugo/content/en/observability_pipelines/destinations/google_cloud_storage.md @@ -53,6 +53,7 @@ You need to have Datadog's [Google Cloud Platform integration][3] installed to s 1. Select the project. 1. Enter the name of the storage bucket you created earlier. 1. Optionally, enter a path. + - **Note**: This path must be a static string. It does not support template syntax, such as `{{ tag_name }}`. To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the destination for your pipeline](#set-up-the-destinations) instead. 1. Optionally, set permissions, add tags, and define the maximum scan size for rehydration. See [Advanced settings][20] for more information. 1. Click **Save**. diff --git a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/amazon_s3/connect_s3_to_datadog_log_archives.en.md b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/amazon_s3/connect_s3_to_datadog_log_archives.en.md index 02758f5e63c..52fa6dd4dc8 100644 --- a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/amazon_s3/connect_s3_to_datadog_log_archives.en.md +++ b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/amazon_s3/connect_s3_to_datadog_log_archives.en.md @@ -8,7 +8,6 @@ 1. Select the AWS account that your bucket is in. 1. Enter the name of the S3 bucket. 1. Optionally, enter a path. - - **Note**: This path must be a static string. It does not support template syntax (for example, `{{ tag_name }}`). To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the Datadog Archives destination for your pipeline][204] instead. 1. Check the confirmation statement. 1. Optionally, add tags and define the maximum scan size for rehydration. See [Advanced settings][202] for more information. 1. Click **Save**. @@ -17,5 +16,4 @@ See the [Log Archives documentation][203] for additional information. [201]: https://app.datadoghq.com/logs/pipelines/log-forwarding [202]: /logs/log_configuration/archives/?tab=awss3#advanced-settings -[203]: /logs/log_configuration/archives -[204]: /observability_pipelines/destinations/datadog_archives/#set-up-the-destination-for-your-pipeline \ No newline at end of file +[203]: /logs/log_configuration/archives \ No newline at end of file diff --git a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/azure_storage/instructions.en.md b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/azure_storage/instructions.en.md index 68eb4f58ac5..f72fab4bc5f 100644 --- a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/azure_storage/instructions.en.md +++ b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/azure_storage/instructions.en.md @@ -31,7 +31,6 @@ Create an [Azure storage account][9051] if you don't already have one. 1. Enter the name of the storage account. 1. Enter the name of the container you created earlier. 1. Optionally, enter a path. - - **Note**: This path must be a static string. It does not support template syntax (for example, `{{ tag_name }}`). To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the Azure Storage destination for your pipeline][9057] instead. 1. Optionally, set permissions, add tags, and define the maximum scan size for rehydration. See [Advanced settings][9055] for more information. 1. Click **Save**. @@ -42,5 +41,4 @@ See the [Log Archives documentation][9056] for additional information. [9053]: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-immutability-policies-manage [9054]: https://app.datadoghq.com/logs/pipelines/log-forwarding [9055]: /logs/log_configuration/archives/?tab=awss3#advanced-settings -[9056]: /logs/log_configuration/archives -[9057]: /observability_pipelines/destinations/azure_storage/#set-up-the-destination-for-your-pipeline \ No newline at end of file +[9056]: /logs/log_configuration/archives \ No newline at end of file diff --git a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/google_cloud_storage/instructions.en.md b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/google_cloud_storage/instructions.en.md index ab819134014..c4b7ae99331 100644 --- a/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/google_cloud_storage/instructions.en.md +++ b/hugo/layouts/shortcodes/observability_pipelines/configure_log_archive/google_cloud_storage/instructions.en.md @@ -25,7 +25,6 @@ 1. Select the project. 1. Enter the name of the storage bucket you created earlier. 1. Optionally, enter a path. - - **Note**: This path must be a static string. It does not support template syntax (for example, `{{ tag_name }}`). To route logs to different object keys based on specific log fields, configure the **Prefix** field when you [set up the Google Cloud Storage destination for your pipeline][9097] instead. 1. Optionally, set permissions, add tags, and define the maximum scan size for rehydration. See [Advanced settings][9095] for more information. 1. Click **Save**. @@ -36,5 +35,4 @@ See the [Log Archives documentation][9096] for additional information. [9093]: https://cloud.google.com/iam/docs/keys-create-delete#creating [9094]: https://app.datadoghq.com/logs/pipelines/log-forwarding [9095]: /logs/log_configuration/archives/?tab=awss3#advanced-settings -[9096]: /logs/log_configuration/archives -[9097]: /observability_pipelines/destinations/google_cloud_storage/#set-up-the-destinations \ No newline at end of file +[9096]: /logs/log_configuration/archives \ No newline at end of file