Skip to content

NodeStatus + plugin update #184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alexandraBara merged 2 commits into from
Apr 13, 2026
Merged

NodeStatus + plugin update #184

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5fe4fb5
NodeStatus + plugin update
alexandraBara Apr 13, 2026
9a96af6
Merge branch 'development' into alex_readme_nodestatus
alexandraBara Apr 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -538,6 +538,17 @@ A plugin config can be used to compare the system data against the config specif
Built-in configs include **NodeStatus** (a subset of plugins) and **AllPlugins** (runs every
registered plugin with default arguments—useful for generating a reference config from the full system).

**NodeStatus plus additional plugins** — built-in configs merge with plugins named after `run-plugins`.
Use **`--plugin-configs=<name>`** (equals form): with a space
after `--plugin-configs`. See below for examples:
```sh
node-scraper --plugin-configs=NodeStatus run-plugins PciePlugin
```

```sh
node-scraper --log-path ./logs --plugin-configs=NodeStatus run-plugins PciePlugin
```

Using a JSON file:
```sh
node-scraper --plugin-configs plugin_config.json
Expand Down
Loading