| 1 | <!--startmeta |
| 2 | custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/integrations/interrupts.md" |
| 3 | meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/metadata.yaml" |
| 4 | sidebar_label: "Interrupts" |
| 5 | learn_status: "Published" |
| 6 | learn_rel_path: "Collecting Metrics/Collectors/Operating Systems" |
| 7 | keywords: ['interrupts'] |
| 8 | message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" |
| 9 | endmeta--> |
| 10 | |
| 11 | # Interrupts |
| 12 | |
| 13 | |
| 14 | <img src="https://netdata.cloud/img/linuxserver.svg" width="150"/> |
| 15 | |
| 16 | |
| 17 | Plugin: proc.plugin |
| 18 | Module: /proc/interrupts |
| 19 | |
| 20 | <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> |
| 21 | |
| 22 | ## Overview |
| 23 | |
| 24 | Monitors `/proc/interrupts`, a file organized by CPU and then by the type of interrupt. |
| 25 | The numbers reported are the counts of the interrupts that have occurred of each type. |
| 26 | |
| 27 | An interrupt is a signal to the processor emitted by hardware or software indicating an event that needs |
| 28 | immediate attention. The processor then interrupts its current activities and executes the interrupt handler |
| 29 | to deal with the event. This is part of the way a computer multitasks and handles concurrent processing. |
| 30 | |
| 31 | The types of interrupts include: |
| 32 | |
| 33 | - **I/O interrupts**: These are caused by I/O devices like the keyboard, mouse, printer, etc. For example, when |
| 34 | you type something on the keyboard, an interrupt is triggered so the processor can handle the new input. |
| 35 | |
| 36 | - **Timer interrupts**: These are generated at regular intervals by the system's timer circuit. It's primarily |
| 37 | used to switch the CPU among different tasks. |
| 38 | |
| 39 | - **Software interrupts**: These are generated by a program requiring disk I/O operations, or other system resources. |
| 40 | |
| 41 | - **Hardware interrupts**: These are caused by hardware conditions such as power failure, overheating, etc. |
| 42 | |
| 43 | Monitoring `/proc/interrupts` can be used for: |
| 44 | |
| 45 | - **Performance tuning**: If an interrupt is happening very frequently, it could be a sign that a device is not |
| 46 | configured correctly, or there is a software bug causing unnecessary interrupts. This could lead to system |
| 47 | performance degradation. |
| 48 | |
| 49 | - **System troubleshooting**: If you're seeing a lot of unexpected interrupts, it could be a sign of a hardware problem. |
| 50 | |
| 51 | - **Understanding system behavior**: More generally, keeping an eye on what interrupts are occurring can help you |
| 52 | understand what your system is doing. It can provide insights into the system's interaction with hardware, |
| 53 | drivers, and other parts of the kernel. |
| 54 | |
| 55 | |
| 56 | |
| 57 | |
| 58 | This collector is supported on all platforms. |
| 59 | |
| 60 | This collector supports collecting metrics from multiple instances of this integration, including remote instances. |
| 61 | |
| 62 | |
| 63 | ### Default Behavior |
| 64 | |
| 65 | #### Auto-Detection |
| 66 | |
| 67 | This integration doesn't support auto-detection. |
| 68 | |
| 69 | #### Limits |
| 70 | |
| 71 | The default configuration for this integration does not impose any limits on data collection. |
| 72 | |
| 73 | #### Performance Impact |
| 74 | |
| 75 | The default configuration for this integration is not expected to impose a significant performance impact on the system. |
| 76 | |
| 77 | ## Setup |
| 78 | |
| 79 | |
| 80 | ### Prerequisites |
| 81 | |
| 82 | No action required. |
| 83 | |
| 84 | ### Configuration |
| 85 | |
| 86 | #### Options |
| 87 | |
| 88 | |
| 89 | |
| 90 | There are no configuration options. |
| 91 | |
| 92 | |
| 93 | |
| 94 | #### via File |
| 95 | |
| 96 | There is no configuration file. |
| 97 | |
| 98 | ##### Examples |
| 99 | There are no configuration examples. |
| 100 | |
| 101 | |
| 102 | |
| 103 | ## Alerts |
| 104 | |
| 105 | There are no alerts configured by default for this integration. |
| 106 | |
| 107 | |
| 108 | ## Metrics |
| 109 | |
| 110 | Metrics grouped by *scope*. |
| 111 | |
| 112 | The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. |
| 113 | |
| 114 | |
| 115 | |
| 116 | ### Per Interrupts instance |
| 117 | |
| 118 | |
| 119 | |
| 120 | This scope has no labels. |
| 121 | |
| 122 | Metrics: |
| 123 | |
| 124 | | Metric | Dimensions | Unit | |
| 125 | |:------|:----------|:----| |
| 126 | | system.interrupts | a dimension per device | interrupts/s | |
| 127 | |
| 128 | ### Per cpu core |
| 129 | |
| 130 | |
| 131 | |
| 132 | Labels: |
| 133 | |
| 134 | | Label | Description | |
| 135 | |:-----------|:----------------| |
| 136 | | cpu | TBD | |
| 137 | |
| 138 | Metrics: |
| 139 | |
| 140 | | Metric | Dimensions | Unit | |
| 141 | |:------|:----------|:----| |
| 142 | | cpu.interrupts | a dimension per device | interrupts/s | |
| 143 | |
| 144 |