惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

腾讯CDC
Microsoft Azure Blog
Microsoft Azure Blog
B
Blog
S
SegmentFault 最新的问题
WordPress大学
WordPress大学
P
Proofpoint News Feed
Hugging Face - Blog
Hugging Face - Blog
MyScale Blog
MyScale Blog
A
About on SuperTechFans
雷峰网
雷峰网
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
T
The Blog of Author Tim Ferriss
MongoDB | Blog
MongoDB | Blog
博客园 - 【当耐特】
The Cloudflare Blog
F
Fortinet All Blogs
小众软件
小众软件
博客园 - 三生石上(FineUI控件)
宝玉的分享
宝玉的分享
罗磊的独立博客
量子位
有赞技术团队
有赞技术团队
V
V2EX
Engineering at Meta
Engineering at Meta

Datadog | The Monitor blog

Introducing our open source AI-native SAST Instrument and monitor Boomi integration flows with OpenTelemetry and Datadog Not all index scans are equal: How we cut query latency by over 99% Platform engineering metrics: What to measure and what to ignore Integrate Recorded Future threat intelligence with Datadog Cloud SIEM CI/CD security: threat modeling using a MITRE-style threat matrix CI/CD security: How to secure your GitHub ecosystem Ingress NGINX is EOL: A practical guide for migrating to Kubernetes Gateway API Operating agentic AI with Amazon Bedrock AgentCore and Datadog LLM Observability: Lessons from NTT DATA Introducing the Datadog Code Security MCP Capture and analyze custom heatmaps in Session Replay Understand session replays faster with AI summaries and smart chapters Monitor ClickHouse query performance with Datadog Database Monitoring How we designed empathetic alert sounds for on-call engineers Search and act across Datadog to resolve issues faster with Bits Assistant Measure the business impact of every product change with Datadog Experiments Analyzing round trip query latency Configuring JavaScript caches for better performance Introducing Bits AI Dev Agent for Code Security Datadog achieves ISO 42001 certification for responsible AI Monitor Nutanix clusters, hosts, and VMs with Datadog Monitor Juniper Mist in Datadog A new Host Map for modern infrastructure Annotate traces to improve LLM quality with Datadog LLM Observability What’s new in Cloud SIEM: AI-powered investigations, enhanced threat intelligence, and scalable security operations Explore Kubernetes with native OpenTelemetry data Monitor Oracle Fusion Cloud Applications with Datadog Announcing the Datadog Terraform provider v4.0.0 Scaling Kubernetes workloads on custom metrics How to design cloud environments for AI-powered threat analysis
Reduce your AWS Step Functions’ error remediation time by...
Jake Greenberg · 2024-10-02 · via Datadog | The Monitor blog

AWS enables customers to retry or redrive Step Functions executions to continue any failed executions of Standard Workflows from their points of failure while maintaining all inputs. For example, if you find broken downstream logic in your code or experience unexpected errors upon execution, you can remediate those errors by fully re-running an execution or use redrive to continue this execution. Previously, the only way for customers to take action on failed Step Functions executions was to leave Datadog and do so in the AWS console. This back and forth between platforms caused a disjointed user experience where customers had to first identify which failed executions to address in Datadog before manually copying that information and executing the retries or redrives in the AWS console.

To overcome this challenge, customers can now find and take action on failed executions directly from the Datadog UI using Datadog App Builder. Executing retry or redrive on failed executions directly from Datadog significantly reduces error remediation time and the need to manually document failed execution ARNs. In this post, we’ll walk through how our support for Step Functions monitoring enables you to quickly remediate errors and reduce costs by redriving executions directly from Datadog.

How to redrive or re-run Step Functions executions directly from Datadog

In order to take advantage of the benefits of redriving or retrying your Step Functions workflow, you must already be monitoring Step Functions using Datadog native Step Functions monitoring (note that this is different from Datadog’s Step Functions integration, which provides access to Step Functions Cloudwatch metrics in Datadog). When redriving or retrying an execution for the first time, you may be prompted to configure an AWS connection. Once you’ve configured your connection, Datadog will remember the connection you’ve chosen and you will not have to reconfigure unless you choose to change your connection, which you can do at any time from the action modal.

After you’ve configured a connection, you will immediately be able to redrive failed Standard Workflows and retry all Workflows that are being monitored on Datadog. Simply navigate to the Serverless view, click on the Step Functions execution you’re troubleshooting, and from that workflow’s State Machine Map click “Redrive from Failed Step” to redrive or “Retry Execution” to retry the Step Functions execution.

Redrive step functions directly from Datadog

Get started today

If you are interested in monitoring your AWS Step Functions effectively, the ability to take action on failed executions directly from the Datadog platform will reduce your time to remediation. As you begin using the feature in your remediation workflows, we would love to hear your thoughts using this form. If you don’t already have a Datadog account, you can sign up for a 14-day free trial to get started.