DefangLabs / DefangLabs/defang
"StartLiveTail, exceeded maximum number of attempts"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 166
- Forks
- 24
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 33
Description
Error: operation error CloudWatch Logs: StartLiveTail, exceeded maximum number of attempts, 3, https response error StatusCode: 400, RequestID: e8f40c05-5a55-45c4-9bf3-e80bee6dc512, LimitExceededException: Rate exceeded
The AWS logger should be able to gracefully handle LimitExceededException. For deployments, only the ECS LogGroup is really important, the others are optional. Could always fall back to polling (query) when live tail fails and/or retry StartLiveTail periodically. For explicit tail/logs, the ECS LogGroup is not important.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Go AWS logger path that calls CloudWatch Logs StartLiveTail and read how deployment and explicit tail/logs flows handle failures. Verify the behavior against rate-limit failures: deployments preserve the ECS LogGroup while optional groups degrade gracefully, and explicit tail/logs do not assume ECS priority.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100