Workflow Templates

Pre-built workflow templates — Daily Health Check, Data Ingestion Monitor, ITSI Episode Analysis, Data Quality Check

Workflow Templates

Pre-built workflow templates automate common Splunk checks. Each template uses a DAG of nodes — tool calls, evaluators, routers, and parallel branches — to produce structured reports.


Available Templates

Daily Health Check

Duration: 2–5 minutes | Complexity: Intermediate | Schedule: Recommended daily (0 9 * * * UTC)

Runs parallel checks across your Splunk deployment:

CheckWhat It Does
Infrastructure DiscoveryMaps search heads, indexers, and forwarders via REST
Indexer HealthCluster health and searchability status
Search Head ResourcesCPU and memory on search heads
License UsageConsumption vs. quota
Data IngestionIngestion rates and data freshness
Forwarder ConnectivityConnection status and throughput
Search PerformanceIdentifies slow searches

All checks run in parallel, then merge at a join node. An evaluator assesses overall severity and a router branches to critical alert, warning report, or healthy summary.

Requires: Splunk MCP


Data Ingestion Monitor

Duration: 1–3 minutes | Complexity: Beginner

Identifies indexes and sourcetypes with no data in the last 60 minutes:

  1. Queries all indexes/sourcetypes and their latest event times.
  2. Evaluator flags any source as STALE if no events in >60 minutes.
  3. Router branches to stale-source analysis or healthy report.

Output: List of stale indexes/sourcetypes, suggested SPL for investigation, and troubleshooting hints.

Requires: Splunk MCP


ITSI Episode Analysis

Duration: 2–5 minutes | Complexity: Intermediate

Analyzes IT Service Intelligence (ITSI) episodes for degraded services:

  1. Fetches episodes from itsi_summary index.
  2. Fetches KPI health per service (runs in parallel with step 1).
  3. Joins episode and KPI data.
  4. Agent analyzes: prioritizes by severity, infers root causes, outputs structured JSON.
  5. Agent generates a human-readable action plan with runbook steps.

Configuration: lookback_hours (default 24), min_severity (default 3)

Requires: Splunk MCP (with ITSI)


Data Quality Check

Duration: 5–7 minutes | Complexity: Intermediate | Schedule: Recommended hourly (0 * * * * UTC)

Runs 7 parallel data quality checks:

CheckWhat It Detects
Ingestion LatencyLag between event time and index time
Timestamp ParsingParsing errors and timezone mismatches
Line BreakingMalformed or truncated multi-line events
DuplicatesDuplicate event detection
Time IssuesFuture-dated events, clock skew
Field CoverageMissing or inconsistent fields
Queue PressureParsing and indexing queue backlogs

Results merge at a join node. Evaluator assesses severity. Router branches to critical alert, warning report, or healthy summary.

Requires: Splunk MCP


How Workflow Nodes Work

Templates use these node types:

Node TypePurpose
startEntry point
endExit point
toolExecutes an MCP tool call (e.g., run SPL query)
agentAI agent reasoning step — analyzes data, generates reports
evaluatorAssesses conditions and sets severity/status
routerConditional branching based on evaluator output
parallel_splitForks execution into parallel branches
parallel_joinWaits for all parallel branches to complete, then merges results

Roadmap Workflows

Additional workflows planned:

  • Security Investigation — correlate security events, identify anomalies
  • Performance Troubleshooting — trace slow searches to root cause
  • Capacity Planning — usage trends and growth projections
  • Data Onboarding Validation — validate new data sources before go-live
  • License Optimization — usage analysis and recommendations

Choosing a Template

NeedTemplate
Routine morning checkDaily Health Check
Missing data alertsData Ingestion Monitor
ITSI service degradationITSI Episode Analysis
Data quality auditData Quality Check
Workflow Templates | Deslicer AI Docs