Skip to content

Clarify behavior without resource collection enabled #33005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Clarify behavior without resource collection enabled #33005

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9c050b3
Update amazon_elastic_container_explorer.md
stzou Nov 21, 2025
89c951b
Update content/en/infrastructure/containers/amazon_elastic_container_…
stzou Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 12 additions & 10 deletions content/en/infrastructure/containers/amazon_elastic_container_explorer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ further_reading:

The Datadog Agent and Datadog Amazon ECS integration can retrieve ECS resources for the [ECS Explorer][1]. This feature enables you to monitor the status of EC2 and Fargate tasks, services, and other ECS components across all of your AWS accounts. You can view resource specifications for tasks within a service and correlate them with related logs, metrics, profiling, and more.

**Note**: The Datadog Agent only reports ECS tasks. Enable AWS Resource Collection to populate all ECS resources.

### Prerequisites

* **[AWS resource collection][10]**: Required for collecting ECS resources.
Expand All @@ -23,7 +25,7 @@ The Datadog Agent and Datadog Amazon ECS integration can retrieve ECS resources

Ensure you have enabled [AWS resource collection][10], the [ECS on EC2 integration][2], and the [ECS on Fargate integration][3].

**Note**: The collection interval for these integrations is approximately 24 hours. To achieve a shorter collection interval of 15 seconds, it is recommended to install the Datadog Agent in your ECS cluster.
**Note**: The collection interval for these integrations is approximately 15 minutes. To achieve a shorter collection interval of 15 seconds, it is recommended to install the Datadog Agent in your ECS cluster.

{{< tabs >}}
{{% tab "Task Definition" %}}
Expand Down Expand Up @@ -176,18 +178,18 @@ Some resources have specific tags. The following tags are available in addition

## Notes and known issues

* Installing the Datadog Agent in your cluster affects how often the ECS Explorer refreshes:
* The Agent and AWS integration setup affects how often the ECS Explorer refreshes:

| **Resource** | **With Datadog Agent** | **Without Datadog Agent** |
|---------------------|------------------------|--------------------------|
| **Cluster** | ~15 minutes | ~15 minutes |
| **Task** | ~15 seconds | ~15 minutes |
| **Task Definition** | ~15 seconds | ~15 minutes |
| **Service** | ~15 seconds | ~15 minutes |
| **Container Instance** | ~15 minutes | ~15 minutes |
| **Resource** | **Resource Collection With Datadog Agent** | **Resource Collection Without Datadog Agent** | **Datadog Agent Without Resource Collection** |
|---------------------|------------------------|--------------------------|--------------------------|
| **Cluster** | ~15 minutes | ~15 minutes | Not Collected |
| **Task** | ~15 seconds | ~15 minutes | ~15 seconds |
| **Task Definition** | ~15 seconds | ~15 minutes | Not Collected |
| **Service** | ~15 seconds | ~15 minutes | Not Collected |
| **Container Instance** | ~15 minutes | ~15 minutes | Not Collected |

* A newly created ECS Service is typically collected within approximately 15 seconds. However, for status changes in an existing Service, a refresh within 15 seconds is not guaranteed.
* Installing the Datadog Agent in your cluster enables visibility into task lifecycle changes. Without the Datadog Agent, stopped tasks can appear as running for up to two days.
* Installing the Datadog Agent in your cluster enables visibility into task lifecycle changes. Without the Datadog Agent, stopped tasks can appear as running for up to 15 minutes.
* Installing the Datadog Agent in your cluster provides additional, relevant host-level tags, such as `availability_zone`.

## Further reading
Expand Down
Loading