Comparison
Progull vs Splunk ITSI.
Splunk ITSI is a powerful observability and service-insight layer. Progull is the agent that actually fixes the abend and closes the ticket.
Capability
Progull
Splunk ITSI
Mainframe abend parsing (S0C7, S322, SB37, SQL-911, U4038)
Via add-ons, manual rules
End-to-end agentic remediation
Closes the ServiceNow incident
Notifies; does not close
JCL resubmit, dataset reallocation, region cycle
Policy-as-code playbooks
Notable Event Aggregation Policies
Event correlation across infra & app
Via integrations
Service-level insight & KPIs
Operational KPIs
Audit trail of remediation actions
Per-decision, immutable
Audit of searches & alerts
They compose
Progull runs alongside Splunk, not against it.
Most customers keep Splunk ITSI as the service-health and observability backbone, and run Progull as the agentic remediation layer for mainframe batch. Telemetry flows both ways via the integrations directory.