Commands
The three PulseNode commands — status, reload and the in-game security GUI.
PulseNode v5.0.2Paper · Spigot1.21 – 1.21.x
PulseNode registers one command with three sub-commands. The command itself requires
pulsenode.admin.
Aliases: /pulsenode, /pn
/pn
perm pulsenode.adminalias /pulsenode
With no argument, prints the status — the same as /pn status.
/pn status
perm pulsenode.admin
Connection state, the last successful post to the API, the configured interval and which collectors are enabled. The first thing to run when the dashboard has stopped updating.
/pn reload
perm pulsenode.admin
Reloads config.yml. Use this after pasting an API key or changing interval — no restart needed.
/pn security
perm pulsenode.admin
Opens the security GUI: recent dangerous commands, connection floods and failed logins, colour-coded by severity. Players only.
If security.enabled is false, it reports that security monitoring is disabled instead.
Anything else prints Usage: /pulsenode [status|reload|security].
Tab completion
/pn completes to status, reload and security.
Console
status and reload work from console. security needs a player, because it opens an inventory
GUI.
Reading /pn status
The three things worth checking, in order:
- Is there an API key? A blank or placeholder key is the single most common cause of "the dashboard shows nothing".
- When was the last successful post? If it is older than a few intervals, the server cannot
reach
pulsenode.tech— check outbound HTTPS. - Which collectors are on? If per-plugin CPU is missing from your reports,
track-pluginsis off or Spark is not installed.
Most problems are the key
An API key belongs to exactly one server. If you copied a config from another server, both are posting to the same dashboard entry and the charts will look like nonsense. Generate a separate key per server.