Softprober Plugins May 2026

Scenario 1: You are referring to the Software/Hardware Inventory Tool (Linux)

If you are a system administrator or a Linux user using the softprober tool (often used for system health, DMI decoding, or hardware inventory), "plugins" usually refer to the modules or extensions used to gather specific data.

How SoftProber Plugins Work: In this context, the tool likely uses a modular architecture to probe different hardware components without taxing the system.

  1. Where to find them:

    • Check the installation directory (usually /usr/lib/softprober/plugins or /usr/share/softprober depending on your distro).
    • Plugins are often shared objects (.so) or executable scripts.
  2. Common Plugin Categories:

    • CPU Plugins: Probe clock speeds, cache sizes, and temperature.
    • Storage Plugins: Interact with smartctl to check hard drive health.
    • Memory Plugins: Read EDID data or check RAM slot usage.
    • Network Plugins: Check interface speeds and driver status.
  3. Troubleshooting Plugins:

    • Permission Errors: Hardware probing plugins often require root privileges. If a plugin fails to load, try running the main command with sudo.
    • Missing Data: If a specific plugin returns "N/A", ensure the relevant kernel modules are loaded (e.g., modprobe eeprom for memory data).

Evaluation criteria for choosing or building plugins

  • Performance overhead (p99 impact, CPU/memory cost)
  • Privacy controls (redaction, sampling, encryption)
  • Safety (non-invasive semantics, crash isolation)
  • Integrations (tracing backends, logs, CI/CD)
  • Configurability (runtime toggles, scoping)
  • Lifecycle management (enable/disable, expiry)
  • Ease of deployment (agent vs code change)
  • Community and maintenance (is the plugin actively maintained and auditable?)

Representative examples (abstracted)

  • A JVM agent that weaves advice around methods with a @Track annotation, exporting spans to OpenTelemetry and allowing runtime toggles via an admin endpoint.
  • An eBPF-based network probe that collects per-pod latency distributions and exposes metrics without modifying app code.
  • A Python import-hook plugin that instruments Flask/Starlette endpoints to capture request metadata and apply schema assertions.
  • An API gateway plugin that validates request/response JSON against a schema, logs violations, and can block malformed calls in production.

Pro-Tips:

  • Order matters: Plugins load in the order listed in Plugins.ini. Put HWiNFO first if other plugins depend on it.
  • Polling intervals: Don't set every plugin to 100ms. Keep HWiNFO at 1000-2000ms to avoid sensor thread collisions.
  • Troubleshooting: Enable Debug=1 in the main config. It logs which plugins fail to load (usually missing VC++ runtimes).

Unlocking the Full Potential of System Monitoring: A Deep Dive into SoftProber Plugins

In the world of high-performance computing, system monitoring is no longer a luxury—it is a necessity. Whether you are an overclocker pushing for a record-breaking benchmark, a data center manager ensuring thermal stability, or a PC enthusiast fine-tuning a custom liquid cooling loop, you need precise, granular data.

While applications like HWMonitor, AIDA64, and HWiNFO are industry staples, SoftProber has carved out a unique niche. Known for its modular architecture and extensive hardware compatibility, SoftProber’s true power is not in its base installation, but in its ecosystem of SoftProber plugins. softprober plugins

These plugins transform a standard sensor reader into a dynamic automation hub. This article explores what SoftProber plugins are, why they are essential, the most critical plugins available, and how to configure them for advanced workflows.

Example Plugin


Here is an example plugin in Java that demonstrates how to implement a simple test plugin:

import softprober.api.SoftproberPlugin;
import softprober.api.test.TestPlugin;
public class MyTestPlugin implements SoftproberPlugin, TestPlugin 
    @Override
    public void init() 
        System.out.println("MyTestPlugin initialized");
@Override
    public void shutdown() 
        System.out.println("MyTestPlugin shut down");
@Override
    public PluginInfo getPluginInfo() 
        return new PluginInfo("MyTestPlugin", "1.0");
@Override
    public void runTest(Test test) 
        System.out.println("Running test: " + test.getName());
        // implement test logic here

2. AquaComputer Ecosystem Plugin

AquaComputer produces high-end water-cooling hardware (D5 Next pumps, Quadro/Octo fan controllers, High Flow sensors). Their proprietary software (AquaSuite) is powerful but isolated. Scenario 1: You are referring to the Software/Hardware

  • What the plugin does: Pulls actual liquid flow rate (L/H), fill level, and conductivity of the coolant directly into SoftProber.
  • Use Case: Create a SoftProber alarm that flashes your keyboard backlight red if the flow rate drops below 100 L/h (indicating a pump failure or air bubble).

Step 1: Choose a Programming Language

Softprober currently supports the following programming languages:

  • Java
  • Python
  • C++

Scenario 2: You are referring to "SoftProber" as a Typo for SoftMaker or similar Software

There is a popular office suite called SoftMaker Office (and previously "SoftMaker FreeOffice"), and users sometimes confuse the name.

If you meant SoftMaker Office:

  • Plugins: SoftMaker does not use a traditional "plugin" system like Chrome or WordPress. Instead, it supports Add-ins and Macros.
  • How to add functionality:
    • You can write Basic scripts or Python scripts to automate tasks.
    • You can install dictionaries (spell check plugins) via the Tools > Options menu.