# Incident Templates Streamline your incident response by automatically creating incidents in your preferred incident management platforms when data pipelines fail. These templates integrate with leading incident management tools to ensure rapid detection, notification, and resolution of data pipeline issues.


📊 Create Datadog Incident	Automatically create Datadog incidents when pipelines fail, integrating data pipeline monitoring with your infrastructure observability platform.	/pages/xqTdbrjqLVERFLURwfev
🔧 Create incident in incident.io	Create incident.io incidents automatically when pipelines fail, leveraging modern incident management workflows for data pipeline issues.	/pages/XdZXHDaUUfl87oGhgNLP
🚨 Create New Relic Incidents	Generate New Relic incidents automatically for failed pipeline runs, enabling immediate incident response through your observability platform.	/pages/nR5Lb3SfYf4UBwcMmMv6
📟 Create PagerDuty Incident	Automatically create PagerDuty incidents when pipelines fail, leveraging your existing on-call rotations for data pipeline monitoring.	/pages/jR0InYCVJ04iAMFYoCks
🔄 Create Rootly Incident	Create Rootly incidents automatically when pipelines fail, utilizing automated incident workflows and Slack-based collaboration.	/pages/pxJdfPiW19nSuU7HXqGc

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/templates/incident-templates.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.