_CORE
AI & Agentic Systems Core Information Systems Cloud & Platform Engineering Data Platform & Integration Security & Compliance QA, Testing & Observability IoT, Automation & Robotics Mobile & Digital Banking & Finance Insurance Public Administration Defense & Security Healthcare Energy & Utilities Telco & Media Manufacturing Logistics & E-commerce Retail & Loyalty
References Technologies Blog Know-how Tools
About Collaboration Careers
CS EN
Let's talk

ITIL Incident Management in Practice

24. 07. 2012 1 min read CORE SYSTEMSdevelopment
ITIL Incident Management in Practice

For two years we handled incidents however we felt like it. No tracking, no metrics. Until a client asked for an SLA report — which didn’t exist.

Classification

P1 Critical: response 15 min, resolution 4h. P2 High: 30 min/8h. P3 Medium: 2h/3 days. P4 Low: 1 day/2 weeks.

JIRA Workflow + Nagios Integration

Custom issue type “Incident” with a workflow and SLA plugin. A CRITICAL alert from Nagios automatically creates a JIRA incident via REST API.

Postmortem

Every P1/P2: What happened? Why? What will we do? We look for systemic causes, not someone to blame. Completed within 48 hours.

Results

SLA compliance: 94 percent. MTTR P1: from 6 hours down to 2.5. Recurring incidents: -30 percent.

itilincident managementjiraprocesy
Share:

CORE SYSTEMS

Stavíme core systémy a AI agenty, které drží provoz. 15 let zkušeností s enterprise IT.

Need help with implementation?

Our experts can help with design, implementation, and operations. From architecture to production.

Contact us