Skip to content

[DOCS-15469] Clarify template syntax for Amazon S3 destination - #39374

Open
maycmlee wants to merge 6 commits into
masterfrom
may/clarify-template-syntax
Open

[DOCS-15469] Clarify template syntax for Amazon S3 destination#39374
maycmlee wants to merge 6 commits into
masterfrom
may/clarify-template-syntax

Conversation

@maycmlee

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <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.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Additional notes

@maycmlee
maycmlee requested a review from a team as a code owner August 20, 2026 19:44
@maycmlee maycmlee added the WORK IN PROGRESS No review needed, it's a wip ;) label Aug 20, 2026
@github-actions github-actions Bot added the Architecture Everything related to the Doc backend label Aug 20, 2026
@github-actions

github-actions Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

@datadog-prod-us1-4

This comment has been minimized.

@github-actions github-actions Bot removed the Architecture Everything related to the Doc backend label Aug 21, 2026

@p-parekh p-parekh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left 2 comments

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we show an example of how the 2 paths can be used together?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

WORK IN PROGRESS No review needed, it's a wip ;)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants