From a5aa6414ecce0d89910300094efcdc264e28c745 Mon Sep 17 00:00:00 2001 From: Brett Blue Date: Fri, 24 Apr 2026 16:07:12 -0600 Subject: [PATCH] [DOCS-12171] Add restart note to JFR template override section Clarify that JFR template overrides are applied at JVM startup and require an application restart to take effect. --- content/en/profiler/profiler_troubleshooting/java.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/profiler/profiler_troubleshooting/java.md b/content/en/profiler/profiler_troubleshooting/java.md index 0b10ea6ad60..8a1c0a985f7 100644 --- a/content/en/profiler/profiler_troubleshooting/java.md +++ b/content/en/profiler/profiler_troubleshooting/java.md @@ -215,6 +215,8 @@ Override templates let you specify profiling properties to override. However, th java -javaagent:/path/to/dd-java-agent.jar -Ddd.profiling.enabled=true -Ddd.logs.injection=true -Ddd.profiling.jfr-template-override-file= -jar path/to/your/app.jar ``` +
JFR template overrides are applied at JVM startup. After you create or modify an override file, restart the application for the changes to take effect.
+ ### Advanced Linux settings for CPU profiles The CPU profiler engine works on most systems, but if the value of `/proc/sys/kernel/perf_event_paranoid` is set to `3`, the profiler can't use perf events to schedule CPU sampling. This results in degraded profile quality, falling back to using itimer. Set `/proc/sys/kernel/perf_event_paranoid` to `2` or lower with the following command: