Users often need to determine if AWS CloudWatch metrics are sufficient for monitoring ECS Fargate environments, or if deploying the Splunk OpenTelemetry Collector provides valuable additional metrics and insight. There can be confusion about the overlap between AWS-Splunk Observability integration and direct Otel Collector use, particularly in relation to custom metrics, application observability, and the need for application instrumentation.
To determine if the Otel Collector is needed, review the following:
Review Metrics Provided by CloudWatch Container Insights:
Assess Monitoring Needs:
Check Existing Integration:
Verify if Application Instrumentation Is Needed:
1. CloudWatch Container Insights Coverage
CloudWatch provides a robust baseline for ECS Fargate infrastructure monitoring, including:
2. Additional Visibility with Splunk OpenTelemetry Collector
The Otel Collector can provide:
3. No Application Instrumentation Needed for Infrastructure Metrics
The Otel Collector collects all infrastructure and custom metrics without the need for APM instrumentation. Only application trace-level data requires explicit instrumentation.
4. References and Documentation
Summary Table: Metric Capabilities
| Metric Type | CloudWatch | Otel Collector |
|---|---|---|
| CPU/Memory Utilization | ✔ | ✔ |
| Network/Disk I/O | ✔ | ✔ |
| Application Custom Metrics | ✔ | |
| Prometheus/StatsD/JMX | ✔ | |
| Per-process Metrics | ✔ | |
| Real-time Granularity | ✔ | |
| APM Tracing (needs app instrumentation) | ✔ |
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |