Applicability
Splunk Application Performance Monitoring
Description
Users running Dockerized applications on either standalone EC2 instances or ECS Fargate may require guidance on how to monitor their infrastructure and application performance with Splunk OTel Collector. This article outlines required steps for each scenario, ensuring full visibility into both container and application telemetry.
Investigation
To determine the appropriate approach:
- Identify if the Dockerized application is running on a standalone EC2 instance or on ECS Fargate.
- Confirm the requirement to monitor container metrics, logs, and application traces.
- Review whether existing monitoring is in place or if this is a new deployment.
Resolution
1. Monitoring Dockerized Applications on Standalone EC2
Deploy the Splunk OTel Collector as an Agent
- Install the Splunk OTel Collector directly on the EC2 instance (as host monitoring agent).
- The collector gathers metrics, logs, and traces from both the host and Docker containers.
Collect Container Metrics
Enable Discovery Mode
- Activate the collector’s discovery mode to automatically detect and configure new containers and services as they are launched.
Collect Container Logs
Instrument Applications
2. Monitoring Dockerized Applications on ECS Fargate
Deploy the Collector as a Sidecar Container
- Add the Splunk OTel Collector as a sidecar container in your ECS task definition (since host installation is not possible in Fargate environments).
Configure Receivers
Instrument Applications
- Instrument the application using OpenTelemetry SDKs or auto-instrumentation agents, and configure them to send data to the collector's OTLP endpoint (typically via localhost).
Use Guided Setup in Splunk Observability Cloud
- Access the Amazon Fargate guided setup:
- Log in to Splunk Observability Cloud.
- Select Data Management > Available integrations > Amazon Fargate.
- Follow the step-by-step instructions to generate your task definition and configuration.
Revision History
| Revision |
Publish Date |
Comments |
1.0 |
01-Oct-2026
|
Initial Release |