Default Workflows

Pre-built workflows that cover common operational patterns, provisioned for every organization as starting points you can extend and customize.

  3 minute read  

Overview

Edge Delta provisions default workflows for every organization. These workflows cover common operational patterns and serve as starting points you can extend and customize.

Each default workflow pairs a monitor or schedule trigger with an SRE teammate analysis step and an email notification action. When a trigger fires, the SRE teammate investigates the alert using available MCP tools, produces a structured JSON analysis, and the workflow emails the findings to your team.

Default Service Anomaly Workflow

This workflow is triggered by the Default Service Anomaly Monitor. When the pattern anomaly monitor detects unusual log patterns, the SRE teammate analyzes what changed compared to baseline, identifies the affected scope (service, pipeline, namespace, or group), estimates whether the anomaly is user-impacting, infers a probable cause, and recommends a next step. The structured analysis is then emailed to the team as an incident summary.

Default Pipeline Liveness Workflow

This workflow is triggered by the Default Pipeline Liveness Monitor. When a pipeline stops reporting heartbeat metrics, the SRE teammate investigates the alert using MCP tools to query metrics, search events, and list pipelines. It identifies which metric triggered the alert and the affected service or tag, estimates severity, infers a probable cause, and recommends an investigation action. The findings are emailed as a structured summary with a link to the investigation in Edge Delta.

Default Company Page Failure Workflow

This workflow is triggered by the Default Company Page Availability Monitor when it enters an alert state. When a synthetic monitor detects a complete page failure, the SRE teammate summarizes what failed and when, checks recent monitor activity over the past 24 hours for related warnings, infers the most likely technical cause, and recommends the next action for an on-call engineer. Results are emailed with the failure time, affected resource, and root cause analysis.

Default Company Page Degradation Workflow

This workflow is triggered by the Default Company Page Availability Monitor when it enters a warning state. When a synthetic monitor detects performance degradation – the service is still responding but approaching failure thresholds – the SRE teammate identifies which metric breached its threshold (latency, timeout, availability), the affected URL or endpoint, and a possible explanation for the degradation. The analysis and recommended next action are emailed to the team.

Default Company Page Daily Summary

This workflow runs on a periodic schedule (daily at 9:00 AM). The SRE teammate searches synthetic monitor events from the past 24 hours and counts alerts and warnings. An If/Else node evaluates the count: if zero, a healthy summary email confirms all monitored endpoints are operating normally. If alerts were detected, a summary of findings is emailed instead. This is the only default workflow that uses a periodic schedule rather than a monitor trigger, demonstrating the Periodic Run trigger type on the Start node.

Customizing default workflows

Default workflows are owned by your organization once provisioned. You can:

  • Edit prompts to match your operational vocabulary
  • Add nodes (for example, Slack or PagerDuty actions alongside email)
  • Change the Start trigger to target different monitors
  • Duplicate a workflow as a template for new patterns
  • Disable or delete workflows you do not need