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
parport0 i7 derive     Interrupt 7, for device(s): parport0
rtc i8 derive     Interrupt 8, for device(s): rtc
acpi i9 derive     Interrupt 9, for device(s): acpi
i8042 i12 derive     Interrupt 12, for device(s): i8042
eth0 i50 derive     Interrupt 50, for device(s): eth0
eth1 i58 derive     Interrupt 58, for device(s): eth1
ehci_hcd:usb1, sata_nv i201 derive     Interrupt 201, for device(s): ehci_hcd:usb1, sata_nv
ohci_hcd:usb2 i209 derive     Interrupt 209, for device(s): ohci_hcd:usb2
megaraid i217 derive     Interrupt 217, for device(s): megaraid
sata_nv i225 derive     Interrupt 225, for device(s): sata_nv
sata_nv i233 derive     Interrupt 233, for device(s): sata_nv
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