Intel-gpu-telegraf
A Docker container that polls utilization statistics from the integrated GPU in Intel CPUs and sends them to InfluxDB via Telegraf, so homelab users can chart…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
26/100 Low
- Maintained
- 0last commit 2361 days ago
- Popular
- 2211 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 75no serious findings
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 35 days ago
- GitHub stars
- 11
- Open issues
- 2
- Last commit
- 2020-06-03
- Activity
- stale
Checked 13 days ago - source: GitHub (brianmiller/docker-intel-gpu-telegraf)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Clone the PMT repo first Clone the Intel PMT repository before running the agent, because the Python script expects to use the pmt.xml sensor-metadata file inside that folder. If the repository or XML path is missing, the agent cannot find the sensor definitions and will not collect data. source
- Install the Python packages Run pip install lxml, requests, and urllib3 before using the Python telemetry agent. These are the libraries the script needs, and missing any of them makes it fail before it can collect data. source
- Run the agent with sudo Start the agent with sudo because it needs elevated permission to access the hardware telemetry source. Without that, the command may start but fail to collect the Intel metrics. source
- GPU Device Access The container needs the /dev/dri GPU device mapped; the Unraid template configures this automatically. source
Fetched 38 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which tool does intel-gpu-telegraf use to collect Intel iGPU utilization?
It collects utilization data from intel_gpu_top.
Can the Intel iGPU be piped to another container such as Plex while using this app?
The source says the author uses the iGPU piped to a Plex container on Unraid while running intel-gpu-telegraf.
Do I need to set up Telegraf configuration files when connecting it to InfluxDB?
The source points to setting up Telegraf configuration files after InfluxDB and Telegraf are running.
Can I enable or disable specific GPU metrics based on the hardware?
Telegraf can be configured to enable or disable metrics based on hardware, including different GPU vendors.
Answers sourced from community.influxdata.com, community.intel.com, forums.unraid.net, github.com
Community
- [Support]: Intel iGPU Utilization Stats into InfluxDB for use ... - Unraid (forum)
- Graphics - Intel Community (other)
- How can I use Telegraf with influxdb - Intel Community (other)
- Enable and disable metrics based on your hardware - Telegraf ... (other)
- Monitoring My Servers with Telegraf, InfluxDB and Grafana (reddit)
Collected 48 days ago - public community threads