/
/
/
1{
2 "manifest": {
3 "description": "Records CPU, memory and event-loop diagnostics of the running server and turns them into a shareable report. Only install this provider temporarily to debug performance issues (or when asked to in a support request) and uninstall it when done - it is not meant for day-to-day use."
4 },
5 "config_entries": {
6 "profiler_note": {
7 "label": "The profiler runs continuously while this provider is installed: a flight recorder samples server health every 10 seconds, an event-loop monitor tracks scheduling delays and (optional) periodic CPU profile windows are captured. Generate the shareable report with the 'profiler/report' API command; the latest report is also written to the 'profiler' folder inside the server data directory. Uninstall this provider when you are done debugging."
8 },
9 "cpu_profile_enabled": {
10 "label": "Periodic CPU profiling",
11 "description": "Automatically capture a CPU profile window at a regular interval. The server runs slightly slower while a window is being captured."
12 },
13 "cpu_profile_duration": {
14 "label": "CPU profile window duration (seconds)",
15 "description": "How long each CPU profile window records before its results are processed."
16 },
17 "cpu_profile_interval": {
18 "label": "CPU profile interval (minutes)",
19 "description": "How often a new CPU profile window is captured automatically."
20 },
21 "action_run_cpu_profile": {
22 "label": "Capture an on-demand CPU profile window, for example while you are reproducing an issue. The result is included in the next report.",
23 "action_label": "Profile now"
24 },
25 "tracemalloc_enabled": {
26 "label": "Track memory allocations (tracemalloc)",
27 "description": "Trace Python memory allocations so the report can show the top allocation sites and their growth between reports. Warning: this roughly doubles memory-tracking overhead and slows the server down while enabled - only use it when hunting a memory leak."
28 }
29 }
30}
31