Plugin Diagnostics

An Unraid plugin that collects diagnostic information for other plugins, helping users troubleshoot plugin-related issues.

  • Monitoring & Logging
  • Plugins
  • Tools & Utilities
An Unraid plugin that collects diagnostic information for other plugins, helping users troubleshoot plugin-related issues.

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.

42/100 Fair

Maintained
77last commit 24 days ago
Popular
00 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 4 days ago

GitHub stars
0
Open issues
2
Last commit
2026-10-28
Latest release
2025.10.21.0220
License
GPL-3.0
Activity
rising

Checked today - source: GitHub (dkaser/unraid-plugin-diagnostics)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Usage & Configuration Run diagnostics from the CLI with `plugin-diagnostics pluginFolder` or from the Unraid WebGUI via the plugin's download page. To tailor output, place a `diagnostics.json` file inside the target plugin's folder under /usr/local/emhttp/plugins; the Title field is mandatory, all other sections are optional, and sed-based substitution filters can redact sensitive values. source
  • Usage Run diagnostics per plugin from the CLI (plugin-diagnostics pluginFolder) or the WebGUI (/plugins/plugin-diagnostics/download.php?plugin=pluginFolder). A plugin opts in by shipping a diagnostics.json file inside its folder under /usr/local/emhttp/plugins; optional sed substitution filters in that file can sanitize output. source
  • Running diagnostics & configuration Install the plugin from the Unraid Apps page, then collect a report for a specific plugin from the CLI with 'plugin-diagnostics <pluginFolder>' or from the WebGUI via the plugin-diagnostics download.php link. To make a plugin reportable, add a diagnostics.json file to that plugin's folder under /usr/local/emhttp/plugins; the 'Title' field is required and unused sections can be omitted. source
  • Installation & Running Install via the Apps (Community Applications) section of your Unraid WebUI. To diagnose a plugin, use the WebGUI endpoint /plugins/plugin-diagnostics/download.php?plugin=<pluginFolder>, or run from the shell: plugin-diagnostics <pluginFolder>. A diagnostics.json file in the plugin's folder under /usr/local/emhttp/plugins controls title and output filters. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I run diagnostics for another Unraid plugin?

Use the CLI command plugin-diagnostics pluginFolder, or use the WebGUI download page for the plugin folder.

Where does the plugin’s diagnostics configuration go?

Place a diagnostics.json file in the plugin folder under /usr/local/emhttp/plugins. The title field is required, and unused sections may be omitted.

Where are diagnostics created from the CLI saved?

They are stored in the logs folder on the flash drive.

How do diagnostics uploads to a support server work?

The plugin first makes a GET request to the upload endpoint with a connect parameter, then POSTs the multipart diagnostics file using the GET response as a Bearer token. The upload server should return a unique identifier for the user to provide with a support request.

Answers sourced from edac.dev, github.com

Community

Collected 48 days ago - public community threads