You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, ECS Tasks are logged to Cloudwatch with a log stream ID that contains the task ID, which is a unique GUID not created until point of execution. This affects how the AWS CLI can be called and what URL to use for monitoring cloudwatch logs via the console.
With the launch of FireLens, there's now an option to parameterize the logging stream ID, which could be used to force a deterministic stream ID and thereby a deterministic CLI command to watch logs, and a deterministic log URL for viewing logs online in Cloudwatch.
Presently, ECS Tasks are logged to Cloudwatch with a log stream ID that contains the task ID, which is a unique GUID not created until point of execution. This affects how the AWS CLI can be called and what URL to use for monitoring cloudwatch logs via the console.
With the launch of FireLens, there's now an option to parameterize the logging stream ID, which could be used to force a deterministic stream ID and thereby a deterministic CLI command to watch logs, and a deterministic log URL for viewing logs online in Cloudwatch.
Related: aws/containers-roadmap#74 (comment)
The text was updated successfully, but these errors were encountered: