<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic AWS Fargate Task Fail Monitoring in Dynatrace tips</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-tips/AWS-Fargate-Task-Fail-Monitoring/m-p/302599#M2127</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We are following&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-into-aws/aws-fargate#runtime" target="_blank"&gt;https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-into-aws/aws-fargate#runtime&lt;/A&gt;&amp;nbsp;to setup Fargate monitoring and it works perfectly for ECS Tasks that is up and running.&lt;/P&gt;&lt;P&gt;Now we have a use case that wants to capture the startup fail, or the ECS Tasks that stopped within 5 minutes, so that we can use Dynatrace as debugging tool without accessing CW logs.&lt;/P&gt;&lt;P&gt;For example, the exit code and the duration that shown in AWS UI (Image attached)&lt;/P&gt;&lt;P&gt;Can you let us know all the possible solutions or workaround. (We consider using AWS CW Metrics Ingestion with Container&amp;nbsp;Insights, but more details to the failure are desired)&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Terry&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jul 2026 01:41:35 GMT</pubDate>
    <dc:creator>TerryL</dc:creator>
    <dc:date>2026-07-30T01:41:35Z</dc:date>
    <item>
      <title>AWS Fargate Task Fail Monitoring</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-tips/AWS-Fargate-Task-Fail-Monitoring/m-p/302599#M2127</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We are following&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-into-aws/aws-fargate#runtime" target="_blank"&gt;https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-into-aws/aws-fargate#runtime&lt;/A&gt;&amp;nbsp;to setup Fargate monitoring and it works perfectly for ECS Tasks that is up and running.&lt;/P&gt;&lt;P&gt;Now we have a use case that wants to capture the startup fail, or the ECS Tasks that stopped within 5 minutes, so that we can use Dynatrace as debugging tool without accessing CW logs.&lt;/P&gt;&lt;P&gt;For example, the exit code and the duration that shown in AWS UI (Image attached)&lt;/P&gt;&lt;P&gt;Can you let us know all the possible solutions or workaround. (We consider using AWS CW Metrics Ingestion with Container&amp;nbsp;Insights, but more details to the failure are desired)&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Terry&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jul 2026 01:41:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-tips/AWS-Fargate-Task-Fail-Monitoring/m-p/302599#M2127</guid>
      <dc:creator>TerryL</dc:creator>
      <dc:date>2026-07-30T01:41:35Z</dc:date>
    </item>
  </channel>
</rss>

