Service graphs

daily graph weekly graph
monthly graph yearly graph

Graph Information

Shows the number of different IRQs received by the kernel. High disk or network traffic can cause a high number of interrupts (with good hardware and drivers this will be less so). Sudden high interrupt activity with no associated higher system activity is not normal.

Field Internal name Type Warn Crit Info
timer i0 derive     Interrupt 0, for device(s): timer
i8042 i1 derive     Interrupt 1, for device(s): i8042
floppy i6 derive     Interrupt 6, for device(s): floppy
rtc i8 derive     Interrupt 8, for device(s): rtc
acpi i9 derive     Interrupt 9, for device(s): acpi
virtio4 i10 derive     Interrupt 10, for device(s): virtio4
uhci_hcd:usb1 i11 derive     Interrupt 11, for device(s): uhci_hcd:usb1
i8042 i12 derive     Interrupt 12, for device(s): i8042
ide1 i15 derive     Interrupt 15, for device(s): ide1
virtio1-virtqueues i50 derive     Interrupt 50, for device(s): virtio1-virtqueues
virtio2-config i177 derive     Interrupt 177, for device(s): virtio2-config
virtio2-requests i185 derive     Interrupt 185, for device(s): virtio2-requests
virtio3-config i193 derive     Interrupt 193, for device(s): virtio3-config
virtio3-requests i201 derive     Interrupt 201, for device(s): virtio3-requests
virtio0-config i209 derive     Interrupt 209, for device(s): virtio0-config
virtio0-input i217 derive     Interrupt 217, for device(s): virtio0-input
virtio0-output i225 derive     Interrupt 225, for device(s): virtio0-output
virtio1-config i233 derive     Interrupt 233, for device(s): virtio1-config
NMI iNMI derive     Nonmaskable interrupt. Either 0 or quite high. If it's normaly 0 then just one NMI will often mark some hardware failure.
LOC iLOC derive     Local (pr. CPU core) APIC timer interrupt. Until 2.6.21 normaly 250 or 1000 pr second. On modern 'tickless' kernels it more or less reflects how busy the machine is.
ERR iERR derive      
MIS iMIS derive