Skip to content

Commit 7f0ad36

Browse files
authored
Update java-standalone-profiler.md
1 parent d89440e commit 7f0ad36

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-monitor/app/java-standalone-profiler.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ The ApplicationInsights Java Agent monitors CPU and memory consumption and if it
6363
Within the profiler user interface (see [profiler settings](../profiler/profiler-settings.md)) there's a **Profile now** button. Selecting this button will immediately request a profile in all agents that are attached to the Application Insights instance.
6464

6565
> [!WARNING]
66-
> Invoking Profile now will enable the profiler feature, as such the default trigger settings for CPU and Memory will apply and if breached profiles will be gathered. If you wish to subsequently disable profiling, this can be done withing the trigger menu as shown in [Installation](#installation).
66+
> Invoking Profile now will enable the profiler feature, and Application Insights will apply default CPU and memory SLA triggers. When your application breaches those SLAs, Application Insights will gather Java profiles. If you wish to disable profiling later on, you can do so within the trigger menu shown in [Installation](#installation).
6767
6868
#### CPU
6969

0 commit comments

Comments
 (0)