SigNoz
Docs
PricingCustomers
Get Started - Free
Docs
IntroductionContributingMigrate from DatadogSigNoz API
OpenTelemetry
What is OpenTelemetryOpenTelemetry Collector GuideOpenTelemetry Demo
Community
Support
Slack
X
Launch Week
Changelog
Dashboard Templates
DevOps Wordle
Newsletter
KubeCon, Atlanta 2025
More
SigNoz vs DatadogSigNoz vs New RelicSigNoz vs GrafanaSigNoz vs Dynatrace
Careers
AboutTermsPrivacySecurity & Compliance
SigNoz Logo
SigNoz
All systems operational
HIPAASOC-2
SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

Monitor ECS Fargate with SigNoz

Overview

ECS Fargate runs containers on serverless compute without exposing the underlying infrastructure. Because you don't have access to the host instances, you need to deploy an OpenTelemetry Collector as a sidecar container within each task you want to observe.

This guide is specific to ECS Fargate. For ECS clusters running on EC2 or External launch types, see Monitor ECS EC2/External which uses a daemon service for host-level collection.

Prerequisites

  • An ECS cluster with Fargate launch type
  • SigNoz Cloud account or Self-Hosted SigNoz
  • AWS CLI access to update task definitions

Why Sidecar on Fargate?

  • No host access: Fargate abstracts the underlying infrastructure
  • No daemon services: Cannot deploy cluster-wide agents like with EC2 launch type
  • The sidecar provides a local OTLP endpoint (localhost) for your app to send traces, metrics, and logs

Architecture

ECS Task (Fargate)
├─ app container(s)
│  └─ sends OTLP telemetry data to the sidecar
├─ signoz-collector sidecar
│  ├─ receives OTLP data from the app container(s)
│  ├─ collects container metrics via AWS ECS metadata
│  └─ exports telemetry to SigNoz (cloud or self-hosted)
└─ log-router (optional, for Fluent Bit log forwarding)

What You Can Collect

Data TypeDescription
Container MetricsCPU, memory, network usage from ECS metadata
Application TracesDistributed traces from instrumented applications
Application LogsLogs forwarded via Fluent Bit log router

Setup

For complete setup instructions, follow the ECS Sidecar Installation Guide.

The setup involves:

  1. Create OTel Collector config in AWS Parameter Store
  2. Add the sidecar container to your ECS task definition
  3. Update IAM roles (Task Execution Role and Task Role) with required permissions
  4. Configure log routing (optional, for application logs via Fluent Bit)
  5. Deploy the updated task definition and verify data in SigNoz

Validate

Once set up, verify your data appears in SigNoz:

  • Logs: Navigate to Logs tab → Logs Explorer
  • Metrics: Navigate to Metrics tab → Metrics Explorer
  • Traces: Navigate to Services tab to see your instrumented applications

Next Steps

  • ECS Sidecar Installation Guide – Complete sidecar setup instructions
  • Send Traces from Applications – Configure application instrumentation

Last updated: December 30, 2025

Edit on GitHub

Was this page helpful?

Your response helps us improve this page.

Prev
EC2/External
Next
EKS
On this page
Overview
Prerequisites
Why Sidecar on Fargate?
Architecture
What You Can Collect
Setup
Validate
Next Steps

Is this page helpful?

Your response helps us improve this page.