Project: Netdata (Observability and Analysis / Observability)
File: intel_gpu.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/intelgpu/README.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/intelgpu/metadata.yaml" sidebar_label: "Intel GPU" learn_status: "Published" learnrelpath: "Collecting Metrics/Hardware Devices and Sensors" most_popular: False message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" endmeta--> <img src="https://netdata.cloud/img/microchip.svg" width="150"/> Plugin: go.d.plugin Module: intelgpu <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> This collector gathers performance metrics for Intel integrated GPUs. It relies on the CLI tool but avoids directly executing the binary. Instead, it utilizes `ndsudo`, a Netdata helper specifically designed to run privileged commands securely within the Netdata environment. This approach eliminates the need to grant the CAPPERFMON capability to `intelgpu_top`, improving security and potentially simplifying permission management. This collector is supported on all platforms. This collector supports collecting metrics from multiple instances of this integration, including remote instances. This integration doesn't support auto-detection. The default configuration for this integration does not impose any limits on data collection. The default configuration for this integration is not expected to impose a significant performance impact on the system. Metrics grouped by scope. The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. These metrics refer to the Intel GPU. This scope has no labels. Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | intelgpu.frequency | frequency | MHz | | intelgpu.power | gpu, package | Watts | These metrics refer to the GPU hardware engine. Labels: | Label | Description | |:--|:-| | engine_class | Engine class (Render/3D, Blitter, VideoEnhance, Video, Compute). | | engine_instance | Engine instance (e.g. Render/3D/0, Video/0, Video/1). | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | intelgpu.enginebusyperc | busy | percentage | There are no alerts configured by default for this integration. Install `intel-gpu-tools` using your distribution's package manager. The configuration file name for this integration is `go.d/intelgpu.conf`. You can edit the configuration file using the `edit-config` script from the Netdata . ```bash cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata sudo ./edit-config go.d/intelgpu.conf ``` The following options can be defined globally: update_every. <details><summary>Config options</summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | update_every | Data collection frequency. | 1 | no | </details> Allows you to override the default data collection interval. <details><summary>Config</summary> ```yaml jobs: name: intelgpu update_every: 5 # Collect Intel iGPU metrics every 5 seconds ``` </details> To troubleshoot issues with the `intelgpu` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`. ```bash cd /usr/libexec/netdata/plugins.d/ ``` Switch to the `netdata` user. ```bash sudo -u netdata -s ``` Run the `go.d.plugin` to debug the collector: ```bash ./go.d.plugin -d -m intelgpu ```