Incident management
Incident management restores an interrupted or degraded IT service as quickly as possible, then keeps a record of what happened.
Updated on 14 November 2026
Definition of incident management
Incident management is the practice that restores an interrupted or degraded IT service as quickly as possible: a device that no longer boots, a full disk, an application that crashes, a connection that drops. It is one of the core practices of ITIL, the IT service management framework.
The aim is not to understand the root cause (that is problem management), but to get the user back to work, fast, and keep a record of what happened.
With LongLife, incident management for devices starts before the user calls: the agent detects the incident, proposes the action and lets you carry it out remotely.
A real-world example
Monday, 9 am, a salesperson reports that her laptop is "crawling". Without a tool, the technician connects, searches, tests. With LongLife, the incident had already been reported on Sunday evening: system disk 97% full, recommended action "free up space", high priority. The technician runs the signed cleanup script remotely, and the salesperson gets her device back fixed without waiting.
The steps, and what LongLife does at each one
| Step | What needs doing | What LongLife gives you |
|---|---|---|
| Detect | Spot the incident, ideally before the user | Detectors that analyse your fleet continuously |
| Prioritise | Rank by urgency and impact | Priority and cost of inaction for each recommended action |
| Diagnose | Understand what is happening on the device | Device page: hardware, software, security, history |
| Resolve | Fix remotely or on site | Remote signed scripts, on-site work orders with QR code |
| Close | Check and keep a record | Automatic resolution when the signal disappears, report for each device, health log |
See a device's recent errors
On a device, Event Viewer shows the recent critical events and errors in the System log, by filtering on these two levels. It is useful for one device, but across a whole fleet nobody does it every day. That is exactly the job of the LongLife detectors.
LongLife, continuous incident management for devices
LongLife installs an agent on every device and turns incident management into a routine:
- continuous detection: detectors analyse your fleet continuously (disk, memory, battery, boot, stability, network, security);
- a clear decision: each incident comes with the recommended action, its priority and the cost of inaction;
- remote resolution: a catalogue of signed scripts, written and tested by OPP!, that grows with every update, confirmation by the user, report for each device;
- on-site intervention: work order with QR code and a technician page that needs no account;
- memory: everything is recorded in the device's health log, which then feeds problem management.
The result: fewer calls to support, incidents dealt with before they are felt, and a clear view of devices at risk. The free plan covers up to 15 devices. Book a meeting to see the incidents in your own fleet, or estimate the impact with the simulator.
For a practical case, read our guide to the PC that is slow to start.
Sources
- AXELOS, ITIL 4 and its service management practices: axelos.com
- Microsoft, reading Windows event logs: learn.microsoft.com
Frequently asked questions
What is an IT incident?
It is an interruption or degradation of an IT service, for example a device that no longer boots, an application that crashes or a network that drops. According to ITIL, incident management aims to restore the service as quickly as possible.
What is the difference between an incident and a problem?
The incident is the symptom, to be dealt with straight away. The problem is the cause, sometimes shared by several incidents, which you then try to eliminate so that the incidents do not come back.
How can incidents be detected before users call?
By monitoring devices continuously. With LongLife, detectors analyse your fleet continuously and propose the action to take, with its priority and the cost of inaction.
What are the steps of incident management?
Detect, log, categorise and prioritise, diagnose, resolve, then close while keeping a record. The earlier the detection, the faster the resolution and the less the user is disrupted.
Read also
Problem management
Problem management looks for the root cause of recurring incidents, to eliminate them instead of fixing them again and again.
Help desk
The help desk is first-level IT support that helps users solve their device, software or access problems.
CMDB
A CMDB (Configuration Management Database) records the components of an IT system, their attributes and the links between them, to know what a failure or a change will affect.
See the real state of your fleet
LongLife measures the health of your Windows devices every day and recommends keeping, upgrading or replacing them, with the cost and CO₂e of each option.