Container orchestration services are becoming more and more popular, as teams are looking to run their container workloads at scale. Kubernetes is already extremely popular, as well as the managed orchestration services by the cloud providers. In particular, AWS’s ECS and Fargate, are commonly used among AWS users, often combined with Lambda functions and other AWS services.

Monitoring ECS and Fargate Workloads

ECS Fargate architecture icons

Using a managed orchestration service brings many benefits since you don’t have to manage it. In addition, it’s more scalable, since the cloud provider does the heavy lifting for you. Monitoring your workloads can be challenging since you have less visibility into what you don’t manage or control.

That’s where Epsagon comes in.

Deploy our CloudFormation integration and be up and running in minutes.

Announcing Epsagon’s ECS and Fargate Monitoring

Epsagon ECS and Fargate Monitoring

Monitor your ECS and Fargate workloads

Epsagon automatically discovers your container workloads, including:

  • ECS clusters
  • EC2 launch type
  • Fargate launch type

The individual tasks are automatically discovered:

ECS and Fargate Container tasks

Container tasks

You can drill down into a service:

Drilling down into a service

Drilling down into a service

And into a task:

Drilling down into a task

Drilling down into a task

Tracing ECS and Fargate Workloads

Epsagon is the only solution that provides automated tracing for ECS and Fargate workloads. Our framework wrappers will automatically detect what needs to be instrumented in your application, with no manual effort from your side. As always with Epsagon, you’ll be up and running in less than 5 minutes.

Tracing container workloads on AWS with Epsagon

Tracing container workloads on AWS with Epsagon

Get Started with Epsagon

Feel free to play around with Epsagon in our demo environment. If you don’t have an Epsagon account, you can sign up to our free trial now.

If you want to get deeper into Epsagon, schedule a 1-1 demo with us.

More from our blog:

Introducing Epsagon’s Trace-Based Alerts and Metrics

The Cost of Monitoring Microservices: Managed Solutions vs. In-house

Getting started with Azure Kubernetes Service (AKS)

AWS CloudWatch Metrics and Dashboards (Part 3)