Cloudwatch metric for when agent kills task
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
Is there a metric for when the agent kills a service due to hard memory limits being exceeded? I am trying to configure cloudwatch alarms for this scenario or the scenario where services can't be placed due to constraints and am having a hard time finding a set of metrics or aggregate metrics that describe this.
If these don't already exist, is it possible to get them added?
Contributor guide
Research direction
Start by reviewing the existing CloudWatch metrics for services killed after hard memory limits and for placement failures caused by constraints. Compare those metrics with the two requested scenarios; done would require a clearly defined metric or aggregate metric for each scenario, but this issue names no files, tests, or implementation entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100