Automate Incident Summary — Operations AI
Operations teams manage complex processes across systems. Manual coordination creates bottlenecks and errors.
26
Fields Extracted
300s
Max Processing
Common Pain Points
- Process delays impact customer satisfaction
- Manual handoffs introduce errors
- Incident response takes too long
- Lack of visibility into operational status
What This Template Does
AI-powered extraction using gemini-2.5-flash. Part of 113 production-ready templates.
Capabilities
- Incident Response
- Monitoring
- Document Processing
- Monitoring
- Operations
Output Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "Incident Summary",
"description": "Incident Summary: Summarise incident timeline and actions from Slack export.",
"type": "object",
"properties": {
"incident_id": {
"type": "string",
"description": "Incident id"
},
"severity": {
"type": "string",
"description": "Severity"
},
"title": {
"type": "string",
"description": "Title"
},
"start_time": {
"type":
...Quick Start
$ pip install doclayer
$ doclayer process document.pdf --agent ops.incident-summary
See It In Action
Real extraction example showing input document and structured output.
Input Document
SLACK EXPORT - #incident-response-20250312 Exported: 2025-03-12 [2025-03-12 14:32:15 UTC] @pagerduty-bot ALERT: Payment API Error Rate > 5% (current: 12.3%) Severity: Critical Triggered by: prometheus-alerts [2025-03-12 14:33:01 UTC] @maria.santos Acknowledging. I'll take IC role. Looking at dashboards now. [2025-03-12 14:34:22 UTC] @maria.santos Seeing elevated 5xx errors on payment-api. Error rate climbing. Now at 15%. Looks like database connection errors in the logs. [2025-03-12 14:35:45
Extracted Data
{
"incident_id": "INC-20250312-001",
"severity": "P1/Critical",
"title": "Payment API Outage - Database Connection Pool Exhaustion",
"start_time": "2025-03-12T14:32:15Z",
"end_time": "2025-03-12T14:52:00Z",
"duration": "19m 45s",
"affected_services": [
"payment-api",
"payments-db-prod",
"pgbouncer"
],
"root_cause": "Long-running analytics query from BI tool caused connection leak, exhausting the database connection pool (0/100 available connections)",
"impact": {
"users_affected": 2500,
"revenue_loss": "Estimated based on 2,500 failed payment attempts",
"description": "All payment methods (credit card, PayPal, bank transfer) were unavailable. Support received approximately 150 customer tickets.",
"error_rate_peak": "15%"
},
"timeline": [
{
"time": "2025-03-12T14:25:00Z",
"event": "Long-running analytics query started (identified later)",
"actor": "BI Tool"
},
{
"time": "2025-03-12T14:32:15Z",
"event": "Alert triggered - Payment API error rate exceeded 5% threshold (12.3%)",
"actor": "prometheus-alerts"
},
{
"time": "2025-03-12T14:33:01Z",
"event": "Incident acknowledged, Incident Commander role assigned",
"actor": "maria.santos"
},
{
"time": "2025-03-12T14:34:22Z",
"event": "Initial diagnosis - Database connection errors identified in logs",
"actor": "maria.santos"
},
{
"time": "2025-03-12T14:35:45Z",
"event": "Database team joined incident response",
"actor": "chen.wei"
},
{
"time": "2025-03-12T14:38:33Z",
"event": "Root cause identified - Connection pool exhausted (0/100 available)",
"actor": "chen.wei"
},
{
"time": "2025-03-12T14:40:15Z",
"event": "Blocking query from BI tool identified as source of connection leak",
"actor": "chen.wei"
},
{
"time": "2025-03-12T14:42:30Z",
"event": "Remediation started - Query terminated, pgbouncer restart initiated",
"actor": "chen.wei"
},
{
"time": "2025-03-12T14:44:18Z",
"event": "pgbouncer restarted, connections recovering",
"actor": "chen.wei"
},
{
"time": "2025-03-12T14:46:55Z",
"event": "Error rate declining to 3%, services recovering",
"actor": "maria.santos"
},
{
"time": "2025-03-12T14:52:00Z",
"event": "Alert resolved - Error rate normalized to 0.4%",
"actor": "prometheus-alerts"
}
],
"participants": [
{
"name": "maria.santos",
"role": "Incident Commander"
},
{
"name": "chen.wei",
"role": "Database Team Responder"
},
{
"name": "pagerduty-bot",
"role": "Alerting System"
}
],
"actions_taken": [
"Acknowledged alert and established incident command",
"Investigated payment-api logs for error patterns",
"Checked database connection pool status",
"Identified blocking analytics query from BI tool",
"Terminated long-running query",
"Restarted pgbouncer to recover connection pool"
],
"resolution": "Terminated blocking analytics query and restarted pgbouncer to restore connection pool availability",
"follow_up_items": [
{
"item": "Add connection pool monitoring alert",
"priority": "high",
"owner": "TBD"
},
{
"item": "Implement query timeout for BI tool connections",
"priority": "high",
"owner": "TBD"
},
{
"item": "Schedule post-incident review",
"priority": "medium",
"owner": "maria.santos"
},
{
"item": "Update runbook for database connection issues",
"priority": "medium",
"owner": "TBD"
}
],
"detection_time": "7 minutes (from query start to alert)",
"time_to_resolution": "19m 45s",
"document_type": "incident_report"
}Slack incident channel export showing critical database connection exhaustion issue on payment API. Demonstrates incident progression, team coordination, root cause identification, and resolution timeline with severity tracking.
Related Templates
Frequently Asked Questions
What documents can Incident Summary process?
The Incident Summary template processes ops documents including various formats and layouts. See the instructions for specific document types supported.
How accurate is the Incident Summary extraction?
The Incident Summary template uses Gemini 2.5 Flash for high-accuracy extraction. Results include confidence scores for each field.
Can I customize the Incident Summary template?
Yes, you can modify the extraction schema, add custom fields, or adjust the instructions to match your specific requirements.
Start Extracting Data Today
Process your first document in under 5 minutes. No credit card required.