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

推荐订阅源

腾讯CDC
aimingoo的专栏
aimingoo的专栏
S
SegmentFault 最新的问题
A
About on SuperTechFans
Engineering at Meta
Engineering at Meta
宝玉的分享
宝玉的分享
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 叶小钗
WordPress大学
WordPress大学
N
Netflix TechBlog - Medium
MyScale Blog
MyScale Blog
Stack Overflow Blog
Stack Overflow Blog
Microsoft Azure Blog
Microsoft Azure Blog
博客园 - 聂微东
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Blog — PlanetScale
Blog — PlanetScale
T
Tailwind CSS Blog
Recent Announcements
Recent Announcements
Jina AI
Jina AI
大猫的无限游戏
大猫的无限游戏
Apple Machine Learning Research
Apple Machine Learning Research
J
Java Code Geeks

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
Instantly respond to changes in your data with Datadog au...
2025-10-07 · via Datadog | The Monitor blog

Datadog Workflow Automation can automate processes and reduce the amount of time spent on time-consuming, repetitive tasks. You can trigger these workflows in real time by tying them to alerts, dashboards, Slack messages, and other signals.

Now, with Datadog Datastore automation rules, you can also trigger workflows whenever data in your datastore is added, updated, or deleted. Datastore is a built-in database in Datadog that complements Workflow Automation and App Builder by letting you store and manage custom business or operational data alongside your observability data. With automation rules, your workflows instantly respond to changes in your datastore, automatically updating any related processes or integrations. As a result, all of your data throughout Datadog stays consistent and up to date without the need for scheduled checks or excessive workflow runs.

In this post, we’ll explore how you can use Datastore automation rules to:

A screenshot of the configuration window for a new automation rule.

Trigger workflows when data is added to a datastore

Datadog Datastore provides flexible, schema-less data storage, making it ideal for tasks such as organizing customer information or tracking app usage. Datastore offers multiple methods for bringing data into Datadog, including via API and Datadog workflows. The API can be especially useful for automated updates to Datastore, enabling you to routinely push data from a variety of sources. By combining these data ingestion methods with automation rules, you can ensure your workflows run on the latest data without any manual effort.

Let’s say you use a separate platform such as GitHub to handle issue tracking, but want to ensure all incidents are tracked in Datadog Incident Management for triage and remediation. Using the Datastore API, you’ve set up automation that pushes incident data from your tracking platform to a dedicated incident datastore whenever a new high-severity issue is created. You can then automatically trigger automation rules to cross-reference the issue data with open incidents in Datadog and, if the incident doesn’t already exist, easily create a new one with the relevant details—such as the severity level—already filled in. This process helps you easily keep multiple systems in sync, enabling both fast response times and robust backups.

A screenshot of a list of workflows you can trigger from an automation rules.
A screenshot of the actions within in a triage workflow.

Keep data fresh throughout your entire system

Datastore acts as a shared data source for apps and workflows within Datadog, so you only have to update your data once to see any changes reflected across your automations. This holds true for automation rules as well. You can manage rules for multiple apps and workflows from within one datastore, making maintenance easier.

Let’s say you use incident status data in a few different workflows:

  • A workflow that collects all of your incident data into a single, customizable app
A screenshot of a custom incident manager app within Datadog.
  • A workflow that sends regular reminders to your on-call responders about unresolved incidents
  • A workflow that handles incident resolution activities, including closing out the relevant tickets and Slack channels
A screenshot of the actions within in an incident resolution workflow.

You already use a datastore to feed these automations up-to-date incident statuses. Within this datastore, you can easily create and manage the automation rules that control when these workflows run.

A screenshot of existing automation rules for a datastore.

In this scenario, you use the Datastore UI to manually mark incidents resolved. You decide to configure your automation rules to trigger each of these workflows whenever the value of the incident status is changed. Therefore, as soon as you mark the incidents in this datastore resolved, the associated workflows automatically start running, ensuring that all resolution activities are handled smoothly.

Fine-tune your automated workflows with Datastore

Datadog already enables you to create specialized workflows with Workflow Automation. With Datastore automation rules, you can make these workflows even more robust by integrating the latest data from your system and users. Tying your workflows to data updates saves you from needing to calculate how often to schedule your runs—or even manually running them yourself—freeing your teams to focus on critical tasks.

You can use the Datadog Datastore documentation to get started with automation rules. Or, if you’re new to Datadog, you can sign up for a 14-day free trial.