[DOCS-15469] Clarify template syntax for Amazon S3 destination - #39374
Open
maycmlee wants to merge 6 commits into
Open
[DOCS-15469] Clarify template syntax for Amazon S3 destination#39374maycmlee wants to merge 6 commits into
maycmlee wants to merge 6 commits into
Conversation
Contributor
This comment has been minimized.
This comment has been minimized.
p-parekh
reviewed
Aug 25, 2026
| 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. |
Contributor
There was a problem hiding this comment.
how does this path work with the path set in OP?
|
|
||
| - 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. |
Contributor
There was a problem hiding this comment.
can we show an example of how the 2 paths can be used together?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes