Place FuniProfiler.jar in the plugins folder and start the server.
Set the registration key in plugins/FuniProfiler/config.yml and restart the server.
Run /fprof. The plugin will provide a private link to this dashboard.
The dashboard owner provides the key. Each server address contains 24 random characters. Anyone with the link can view its statistics.
LIVE MONITORING
Server
CPU usage
% of one core
100% = one fully utilized core
JVM memory
Heap · MiB
Java object memory
Tick time
MSPT · ms
At 20 TPS, each tick has a 50 ms budget
Players online
Players
Connected players over time
Resource breakdown
Plugins and server categories over the selected period
JFR
CPU is the share of sampled execution stacks, not exact CPU time. Allocated memory estimates created objects, including those already garbage-collected. It is not the RAM retained by a plugin.
Source
CPU sample share
Samples
Allocated memory ≈
Memory leak
Shared library classes are not attributed to a specific plugin. JVM categories are inferred from class names in the stack.
Worlds & entities
Latest sample
World
Players
Loaded chunks
Entities
Living entities
Memory diagnostics
Observation
Not enough data
Confirming a leak in a specific plugin requires analysis of retained objects and reference chains in heap dumps. A rising chart or high allocation rate does not prove a leak.