CAP-2761 Add recommended ecs_fargate monitors

[stzou]

What does this PR do?

Add recommended ECS Fargate monitors

Motivation

CAP-2761 - part of OKR to improve the overall ECS alerting and troubleshooting experience in Datadog.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[github-actions]

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

Review from steveny91 is dismissed. Related teams and files:

• agent-integrations
  • ecs_fargate/assets/monitors/ecs_fargate_cpu_usage.json
  • ecs_fargate/assets/monitors/ecs_fargate_ephemeral_storage.json
  • ecs_fargate/assets/monitors/ecs_fargate_mem_usage.json
  • ecs_fargate/assets/monitors/ecs_fargate_net_rcvd.json
  • ecs_fargate/assets/monitors/ecs_fargate_net_sent.json

[sumedham]

LGTM!

1. We discussed this on slack but over time, we want to drive customers to the ECS Page, as soon as the slack message comes through in whatever #ops channel they may have. Here is a monitor example that does well with deep links and has shown more drive to the Serverless page.
2. When looking at metrics most used in monitors I noticed that ecs.fargate.mem.hierarchical_memory_limit is used quite a bit by some customers. Is there any reason customers would use that?

Review from sblumenthal is dismissed. Related teams and files:

• container-integrations
  • ecs_fargate/assets/monitors/ecs_fargate_cpu_usage.json
  • ecs_fargate/assets/monitors/ecs_fargate_ephemeral_storage.json
  • ecs_fargate/assets/monitors/ecs_fargate_mem_usage.json
  • ecs_fargate/assets/monitors/ecs_fargate_net_rcvd.json
  • ecs_fargate/assets/monitors/ecs_fargate_net_sent.json

[stzou]

2. When looking at metrics most used in monitors I noticed that ecs.fargate.mem.hierarchical_memory_limit is used quite a bit by some customers. Is there any reason customers would use that?

ecs.fargate.mem.hierarchical_memory_limit reports the mem limit for containers without an explicit memory limit defined. In the case of ecs containers, it will be the task mem limit. The use case for this metric would be to receive alerts when the sum all containers' resource usage in a task are approaching the task limit. This use case if covered by the cpu and mem monitors.