architektapx/prtgsensorkit — explained in plain English
Analysis updated 2026-05-18
Write a custom PRTG sensor that reports CPU, disk, or API metrics without manually formatting JSON.
Securely store API tokens or credentials for a monitoring script using built-in encrypted secret storage.
Calculate rate-of-change metrics between sensor runs using the built-in state caching helpers.
Diagnose common mistakes in an existing PRTG sensor script before deploying it.
| architektapx/prtgsensorkit | bjdubb/codex-full-output | chawyehsu/base16-concfg | |
|---|---|---|---|
| Stars | 8 | 6 | 10 |
| Language | PowerShell | PowerShell | PowerShell |
| Last pushed | — | — | 2026-06-17 |
| Maintenance | — | — | Maintained |
| Setup difficulty | easy | moderate | easy |
| Complexity | 3/5 | 3/5 | 1/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires PRTG Network Monitor and installing the module for the correct PowerShell host bitness.
PrtgSensorKit is a PowerShell toolkit that makes it much easier to write custom monitoring sensors for PRTG, a popular network and system monitoring tool. Normally, writing a custom sensor for PRTG means manually formatting output in a specific structure and carefully following a long list of rules, and getting any detail wrong can cause the sensor to silently fail. This toolkit takes over that repetitive plumbing so you can focus on the part that actually collects the data you care about, such as CPU usage or disk space. With this framework, you write a small script block containing just the logic for gathering your metric, hand it to a single command, and the toolkit builds the properly formatted result for you. It automatically enforces PRTG's rules, such as a maximum of fifty measurement channels per sensor and message length limits, and it catches errors in your code and turns them into a proper PRTG error message instead of letting your sensor crash silently. The toolkit also includes several convenience features beyond basic formatting. It offers a secure way to store passwords and API tokens using Windows' built in encryption instead of writing them directly into your script, a way to save small pieces of information between runs so you can calculate rates of change over time, automatic retry logic for unreliable operations, and a helper to fix an older PowerShell security setting that can otherwise block modern web requests. There is also a diagnostic tool that checks your sensor script for common mistakes before you deploy it to PRTG. Because PRTG always starts custom sensors using an older 32 bit version of Windows PowerShell, the documentation carefully explains where the toolkit and your own script's dependencies need to be installed, and includes helper commands to relaunch your script in 64 bit PowerShell or PowerShell 7 when your sensor code specifically needs that. The project is installed as a standard PowerShell module and is released under the MIT license, meaning it can be used and modified freely, including for commercial monitoring setups.
A PowerShell framework that removes boilerplate and guarantees valid output when building custom PRTG monitoring sensors.
Mainly PowerShell. The stack also includes PowerShell.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.