Add guidance for automatic tag enrichment with lambda forwarder setup #22027
Conversation
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
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
stzou force-pushed the stzou/ecs-fargate-forwarder branch from 2d4fa8b to c62cfb0 Compare 
rtrieu approved these changes Dec 2, 2025
temporal-github-worker-1 bot added docs/approved and removed docs/review-requested labels 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?
Add guidance around setting the log group and stream name when configuring ECS fargate log collection with the lambda forwarder.
Motivation
We automatically enrich ECS fargate logs with relevant ECS tags submitted from a lambda forwarder, but this feature requires additional configurations that are not documented yet.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged