Repository: DataDog/documentation
Pull request #29406: Added new page for automated analysis, as well as screenshots
Author: login: brantigua
Labels: name: Architecture
description: Everything related to the Doc backend
name: editorial review
description: Waiting on a more in-depth review
name: Images
description: Images are added/removed with this PR
name: mergequeue-status: done
name: okr11
Created: 2025-05-16T21:06:22Z | Merged: 2025-05-19T21:10:02Z

<!-- *Note: Please remember to review the Datadog Documentation [Contribution Guidelines](https://github.com/DataDog/documentation/blob/master/CONTRIBUTING.md) if you have not yet done so.* -->

### What does this PR do? What is the motivation?
<!-- A brief description of the change being made with this pull request. What is your motivation for the PR? -->
This PR is to add documentation for our new feature: **Automated Analysis**. This includes general explanations, where to find the analysis, as well as a list of current insights.

### Merge instructions

<!-- 
If you're waiting for a release or there are other considerations that you want us to be aware of, list them here. 
If the PR is ready to be merged once it receives the required reviews, check the box below after you've created the PR.
-->

Merge readiness:
- [x] Ready for merge

**For Datadog employees**:
Merge queue is enabled in this repo. Your branch name MUST follow the `<name>/<description>` convention and include the forward slash (`/`). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

```
/merge
```

### Additional notes
<!-- Anything else we should know when reviewing?-->

<!-- Previewing the PR: Assuming you are a Datadog employee and named your branch `<yourname>/<description>`, a preview build will run and links to the preview output will be auto-generated and posted in the PR comments. The links will 404 until the preview build is finished running. -->



Diff:
diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml
index d4e253c1a05..13ff86e4b22 100644
--- a/config/_default/menus/main.en.yaml
+++ b/config/_default/menus/main.en.yaml
@@ -4093,56 +4093,61 @@ menu:
       parent: profiler
       identifier: profiler_compare
       weight: 5
+    - name: Automated Analysis
+      url: profiler/automated_analysis
+      parent: profiler
+      identifier: profiler_automated_analysis
+      weight: 6
     - name: Profiler Troubleshooting
       url: profiler/profiler_troubleshooting/
       parent: profiler
       identifier: profiler_troubleshooting
-      weight: 6
+      weight: 7
     - name: Java
       url: profiler/profiler_troubleshooting/java/
       parent: profiler_troubleshooting
       identifier: profiler_troubleshooting_java
-      weight: 601
+      weight: 701
     - name: Python
       url: profiler/profiler_troubleshooting/python/
       parent: profiler_troubleshooting
       identifier: profiler_troubleshooting_python
-      weight: 602
+      weight: 702
     - name: Go
       url: profiler/profiler_troubleshooting/go/
       parent: profiler_troubleshooting
       identifier: profiler_troubleshooting_go
-      weight: 603
+      weight: 703
     - name: Ruby
       url: profiler/profiler_troubleshooting/ruby/
       parent: profiler_troubleshooting
       identifier: profiler_troubleshooting_ruby
-      weight: 604
+      weight: 704
     - name: Node.js
       url: profiler/profiler_troubleshooting/nodejs/
       parent: profiler_troubleshooting
       identifier: profiler_troubleshooting_nodejs
-      weight: 605
+      weight: 705
     - name: .NET
       url: profiler/profiler_troubleshooting/dotnet/
       parent: profiler_troubleshooting
       identifier: profiler_troubleshooting_dotnet
-      weight: 606
+      weight: 706
     - name: PHP
       url: profiler/profiler_troubleshooting/php/
       parent: profiler_troubleshooting
       identifier: profiler_troubleshooting_php
-      weight: 607
+      weight: 707
     - name: C/C++/Rust
       url: profiler/profiler_troubleshooting/ddprof/
       parent: profiler_troubleshooting
       identifier: profiler_troubleshooting_linux
-      weight: 608
+      weight: 708
     - name: Guides
       url: profiler/guide/
       parent: profiler
       identifier: profiler_guides
-      weight: 7
+      weight: 8
     - name: Database Monitoring
       url: database_monitoring/
       pre: database-2
diff --git a/content/en/profiler/automated_analysis.md b/content/en/profiler/automated_analysis.md
new file mode 100644
index 00000000000..599e211d695
--- /dev/null
+++ b/content/en/profiler/automated_analysis.md
@@ -0,0 +1,72 @@
+---
+title: Automated Analysis
+description: Automatically surface critical issues with contextual insights and recommended next steps
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+---
+
+## Overview
+Automated Analysis automatically detects performance issues in your applications using Continuous Profiler data and provides actionable insights for resolution. When an issue is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (for example, affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue
+
+This reduces the profiling expertise needed to identify and resolve performance issues in your applications that might otherwise go unnoticed.
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Access Automated Analysis from the [Profile explorer][1]. Insights are displayed:
+
+- In the **Top Insights** banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
+
+- In the **Insights** column within the service list
+{{< img src="profiler/profiling_automated_analysis_column.png" alt="The Automated Analysis column displaying insights detected for a given service within the service list" style="width:100%;">}}
+
+- Within a flame graph view
+{{< img src="profiler/profiling_automated_analysis_flamegraph_viz.png" alt="The Automated Analysis column displaying insights detected for a given service within a flamegraph" style="width:100%;">}}
+
+- Within a timeline view
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Automated Analysis column displaying insights detected for a given service within a timeline" style="width:100%;">}}
+
+Click an insight to see a high-level summary that explains the issue, contextual insights from profiling data, and recommended next steps.
+{{< img src="profiler/profiling_automated_analysis_details.png" alt="Expanded Profiling Insights showing the details of a detected Issue" style="width:100%;">}}
+
+## Supported insights
+
+Automated Analysis supports finding the following insights:
+
+| Name                      | Severity | Description |
+|---------------------------|----------|-------------|
+| Duplicated Flags          | Info     | Triggers if duplicate flags were provided to the runtime (for example, `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect. |
+| Explicit GC               | Info     | Triggers if there are System.gc() calls. |
+| GC Pause Peak Duration    | Info     | Triggers if at least one GC pause took more than 1 second. |
+| GC Setup                  | Info     | Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread |
+| Head of line blocking     | Info     | Triggers if a queue event gets stuck behind the given activity. |
+| Primitive Value Boxing    | Info     | Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions. |
+| Deadlocked Threads Detected | Warn   | Triggers if max number of deadlocked threads over query context is bigger than 0. |
+| GC Pauses                 | Warn     | Triggers if more than 10% of time was spent in GC pauses. |
+| Options                   | Warn     | Triggers if undocumented, deprecated or non-recommended option flags were detected. |
+| Stackdepth Setting        | Warn     | Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data. |
+| Thrown Exceptions         | Warn     | Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defaults to 10K) |
+| VMOperation Peak Duration | Warn     | Triggers if a blocking VM operation (or combination of operations close in time) takes more than 2 seconds. Reports details about the operation with the highest duration. |
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://app.datadoghq.com/profiling/explorer
+
diff --git a/content/en/profiler/connect_traces_and_profiles.md b/content/en/profiler/connect_traces_and_profiles.md
index 9a48080c33a..b299f73eb3e 100644
--- a/content/en/profiler/connect_traces_and_profiles.md
+++ b/content/en/profiler/connect_traces_and_profiles.md
@@ -116,15 +116,18 @@ The Trace to Profiling integration is enabled when you [turn on profiling for yo
 
 ### Span execution timeline view
 
-{{< img src="profiler/profiles_tab.png" alt="Profiles tab has a timeline view that breaks down threads and execution over time" >}}
+{{< img src="profiler/profiling_automated_analysis_individual.png" alt="Profiles tab has a timeline view that breaks down threads and execution over time" >}}
 
-The timeline view surfaces time-based patterns and work distribution over the period of the span.
+The timeline view surfaces time-based patterns and work distribution over the period of the span. It provides a visual breakdown of how threads contributed to the request over time.
 
 With the span timeline view, you can:
 
-- Isolate time-consuming methods.
-- Sort out complex interactions between threads.
-- Surface runtime activity that impacted the request.
+- Isolate time-consuming methods
+- Sort out complex interactions between threads
+- Surface runtime activity that impacted the request
+- Leverage [Automated Analysis][1] to highlight performance issues directly in the view, such as oversized thread pools or GC contention
+
+[1]: /profiler/automated_analysis/
 
 Depending on the runtime and language, the lanes vary:
 
diff --git a/static/images/profiler/profiling_automated_analysis.png b/static/images/profiler/profiling_automated_analysis.png
new file mode 100644
index 00000000000..18197ecfeec
Binary files /dev/null and b/static/images/profiler/profiling_automated_analysis.png differ
diff --git a/static/images/profiler/profiling_automated_analysis_aggregated.png b/static/images/profiler/profiling_automated_analysis_aggregated.png
new file mode 100644
index 00000000000..5d8c1a5559a
Binary files /dev/null and b/static/images/profiler/profiling_automated_analysis_aggregated.png differ
diff --git a/static/images/profiler/profiling_automated_analysis_banner.png b/static/images/profiler/profiling_automated_analysis_banner.png
new file mode 100644
index 00000000000..be1405efbf0
Binary files /dev/null and b/static/images/profiler/profiling_automated_analysis_banner.png differ
diff --git a/static/images/profiler/profiling_automated_analysis_column.png b/static/images/profiler/profiling_automated_analysis_column.png
new file mode 100644
index 00000000000..b236845a4d4
Binary files /dev/null and b/static/images/profiler/profiling_automated_analysis_column.png differ
diff --git a/static/images/profiler/profiling_automated_analysis_details.png b/static/images/profiler/profiling_automated_analysis_details.png
new file mode 100644
index 00000000000..01c984e1aa8
Binary files /dev/null and b/static/images/profiler/profiling_automated_analysis_details.png differ
diff --git a/static/images/profiler/profiling_automated_analysis_flamegraph_viz.png b/static/images/profiler/profiling_automated_analysis_flamegraph_viz.png
new file mode 100644
index 00000000000..298ebc445a9
Binary files /dev/null and b/static/images/profiler/profiling_automated_analysis_flamegraph_viz.png differ
diff --git a/static/images/profiler/profiling_automated_analysis_individual.png b/static/images/profiler/profiling_automated_analysis_individual.png
new file mode 100644
index 00000000000..5c122c479d3
Binary files /dev/null and b/static/images/profiler/profiling_automated_analysis_individual.png differ


Reviews:
user: login: brett0000FF
body: Looking good--thanks for the draft! Let me know if you have any questions about my suggestions. Please feel free to disagree with any of them. 🙂 
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-19T16:47:15Z
user: login: brett0000FF
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-19T16:55:36Z
user: login: brantigua
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-19T17:16:23Z
user: login: brantigua
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-19T17:18:53Z
user: login: brett0000FF
body: Note I switched to use a normal markdown table. Happy to revert if you disagree before we merge. Thanks!
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-19T20:24:19Z

Review comments:
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: High-level question, but what's the reason we call this Automated Analysis instead of Recommendations like we have for [APM](https://github.com/DataDog/documentation/pull/29347), [CCM](https://docs.datadoghq.com/cloud_cost_management/recommendations/), [DBM](https://docs.datadoghq.com/database_monitoring/recommendations/)?
created_at: 2025-05-19T16:14:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
- Contextual insights from profiling data (for example, affected methods, packages, or processes)
```
created_at: 2025-05-19T16:15:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: Note: Let's crop out the sidebar or blur your name from the screenshots.
created_at: 2025-05-19T16:20:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
Automated Analysis automatically detects performance issues in your applications using Continuous Profiler data and provides actionable insights for resolution. When an issue is detected, Automated Analysis provides:
```
created_at: 2025-05-19T16:30:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
- Recommended next steps to help you resolve the issue
```
created_at: 2025-05-19T16:31:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
This reduces the profiling expertise needed to identify and resolve performance issues in your applications that might otherwise go unnoticed.
```


created_at: 2025-05-19T16:35:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
Access Automated Analysis from the [Profile explorer][1]. Insights are displayed:
```
created_at: 2025-05-19T16:37:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
- In a banner at the top of the page when you're scoped to a specific service
```
created_at: 2025-05-19T16:37:37Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
+- As a column within the service list
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
- In a column within the service list
```
created_at: 2025-05-19T16:38:08Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
+- As a column within the service list
+{{< img src="profiler/profiling_automated_analysis_column.png" alt="The Automated Analysis column displaying insights detected for a given service within the service list" style="width:100%;">}}
+
+Clicking an an insight in either area will display a high-level summary explaining the issue, contextual insights from profiling data, and  recommended next steps.
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
Click an insight to see a high-level summary that explains the issue, contextual insights from profiling data, and recommended next steps.
```
created_at: 2025-05-19T16:39:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
+- As a column within the service list
+{{< img src="profiler/profiling_automated_analysis_column.png" alt="The Automated Analysis column displaying insights detected for a given service within the service list" style="width:100%;">}}
+
+Clicking an an insight in either area will display a high-level summary explaining the issue, contextual insights from profiling data, and  recommended next steps.
+{{< img src="profiler/profiling_automated_analysis_details.png" alt="Expanded Profiling Insights showing the details of a detected Issue" style="width:100%;">}}
+
+## Aggregated vs Individual Insights
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
## Aggregated vs individual insights
```
created_at: 2025-05-19T16:41:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
+- As a column within the service list
+{{< img src="profiler/profiling_automated_analysis_column.png" alt="The Automated Analysis column displaying insights detected for a given service within the service list" style="width:100%;">}}
+
+Clicking an an insight in either area will display a high-level summary explaining the issue, contextual insights from profiling data, and  recommended next steps.
+{{< img src="profiler/profiling_automated_analysis_details.png" alt="Expanded Profiling Insights showing the details of a detected Issue" style="width:100%;">}}
+
+## Aggregated vs Individual Insights
+Individual insights are tied to a specific profile and show up directly in the flamegraph and timeline views. They highlight problems detected within a single recording, giving detailed context about a specific performance issue observed in that exact moment.
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
**Individual insights** appear within specific profiles in the flamegraph and timeline views. They highlight issues detected in a single recording, providing detailed context about problems at a specific moment in time.
```


created_at: 2025-05-19T16:41:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
+- As a column within the service list
+{{< img src="profiler/profiling_automated_analysis_column.png" alt="The Automated Analysis column displaying insights detected for a given service within the service list" style="width:100%;">}}
+
+Clicking an an insight in either area will display a high-level summary explaining the issue, contextual insights from profiling data, and  recommended next steps.
+{{< img src="profiler/profiling_automated_analysis_details.png" alt="Expanded Profiling Insights showing the details of a detected Issue" style="width:100%;">}}
+
+## Aggregated vs Individual Insights
+Individual insights are tied to a specific profile and show up directly in the flamegraph and timeline views. They highlight problems detected within a single recording, giving detailed context about a specific performance issue observed in that exact moment.
+{{< img src="profiler/profiling_automated_analysis_individual.png" alt="Example of an individual profile insight within the trace explorer" style="width:100%;">}}
+
+Aggregated insights, on the other hand, are surfaced at the service level and represent patterns detected across many profiles. They help you identify recurring or systemic issues affecting a service over time, making them ideal for quickly spotting problematic trends without digging into individual profiles.
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
Aggregated insights, on the other hand, are surfaced at the service level and represent patterns detected across many profiles. They help you identify recurring or systemic issues affecting a service over time, making them ideal for quickly spotting problematic trends without digging into individual profiles.
```

**Aggregated insights** appear at the service level and represent patterns detected across multiple profiles over time. They help you identify recurring or systemic issues affecting your service.
created_at: 2025-05-19T16:42:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
+- As a column within the service list
+{{< img src="profiler/profiling_automated_analysis_column.png" alt="The Automated Analysis column displaying insights detected for a given service within the service list" style="width:100%;">}}
+
+Clicking an an insight in either area will display a high-level summary explaining the issue, contextual insights from profiling data, and  recommended next steps.
+{{< img src="profiler/profiling_automated_analysis_details.png" alt="Expanded Profiling Insights showing the details of a detected Issue" style="width:100%;">}}
+
+## Aggregated vs Individual Insights
+Individual insights are tied to a specific profile and show up directly in the flamegraph and timeline views. They highlight problems detected within a single recording, giving detailed context about a specific performance issue observed in that exact moment.
+{{< img src="profiler/profiling_automated_analysis_individual.png" alt="Example of an individual profile insight within the trace explorer" style="width:100%;">}}
+
+Aggregated insights, on the other hand, are surfaced at the service level and represent patterns detected across many profiles. They help you identify recurring or systemic issues affecting a service over time, making them ideal for quickly spotting problematic trends without digging into individual profiles.
+{{< img src="profiler/profiling_automated_analysis_aggregated.png" alt="Example of an aggregated insight within the profiler explorer" style="width:100%;">}}
+
+
+## Supported Insights
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: ```suggestion
## Supported insights
```
created_at: 2025-05-19T16:42:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -116,15 +116,18 @@ The Trace to Profiling integration is enabled when you [turn on profiling for yo
 
 ### Span execution timeline view
 
-{{< img src="profiler/profiles_tab.png" alt="Profiles tab has a timeline view that breaks down threads and execution over time" >}}
+{{< img src="profiler/profiling_automated_analysis_individual.png" alt="Profiles tab has a timeline view that breaks down threads and execution over time" >}}
 
-The timeline view surfaces time-based patterns and work distribution over the period of the span.
+The timeline view surfaces time-based patterns and work distribution over the period of the span. It provides a visual breakdown of how threads contributed to the request over time.
 
 With the span timeline view, you can:
 
-- Isolate time-consuming methods.
-- Sort out complex interactions between threads.
-- Surface runtime activity that impacted the request.
+- Isolate time-consuming methods
+- Sort out complex interactions between threads
+- Surface runtime activity that impacted the request
+- Leverage [Automated Analysis][1] to highlight performance issues directly in the view, such as oversized thread pools or GC contention
+
+[1]: https://www.datadoghq.com//profiler/automated_analysis/
path: content/en/profiler/connect_traces_and_profiles.md
user: login: brett0000FF
body: ```suggestion
[1]: /profiler/automated_analysis/
```
created_at: 2025-05-19T16:46:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
+
+
+{{< img src="profiler/profiling_automated_analysis.png" alt="The Profiler Thread Time line showing a Thrown Exception insight" style="width:100%;" >}}
+
+## Explore insights
+Automated Analysis will be surfaced within the [Profile explorer][1]
+- As a banner at the top of the page when you're scoped to a specific service
+{{< img src="profiler/profiling_automated_analysis_banner.png" alt="The Automated Analysis banner displaying insights detected for a given service" style="width:100%;">}}
path: content/en/profiler/automated_analysis.md
user: login: brett0000FF
body: Pushed commit here! https://github.com/DataDog/documentation/pull/29406/commits/1ec19bb3929df03bc68733c50e748742ccfcdee3
created_at: 2025-05-19T16:55:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
path: content/en/profiler/automated_analysis.md
user: login: brantigua
body: I've pushed for that in the past but many of these insights are missing a vital piece to make then a Recommendation which is: always having a clear impact statement. 

We can say that the findings here can help with a given issue, but it's hard to definitely tie that to an impact (example: fixing GC issues will reduce CPU load but we can't concretely say by how much due to many other factors). However, when we do have that info, we promote that insight and it will show up in APM recommendations
created_at: 2025-05-19T17:16:22Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: Automated Analysis
+description: Automatically surfacing critical issues with contextual insights and recommended next steps
+aliases:
+    - /profiler/automated_analysis/
+further_reading:
+    - link: 'profiler/enabling'
+      tag: 'Documentation'
+      text: 'Enable continuous profiler for your application'
+    - link: 'getting_started/profiler'
+      tag: 'Documentation'
+      text: 'Getting Started with Profiler'
+    - link: 'https://www.datadoghq.com/blog/introducing-datadog-profiling/'
+      tag: 'Blog'
+      text: 'Introducing always-on production profiling in Datadog'
+    - link: 'https://www.datadoghq.com/blog/continuous-profiler-timeline-view/'
+      tag: 'Blog'
+      text: "Diagnose runtime and code inefficiencies using Continuous Profiler's timeline view"
+multifiltersearch:
+  # "id" must match the corresponding key in the "data" object
+  headers:
+    - name: Name
+      id: name
+      filter_by: true
+    - name: Severity
+      id: severity
+      filter_by: true
+    - name: Description
+      id: description
+      filter_by: false
+      
+  data:
+    - name: GC Setup
+      severity: Info
+      description: Triggers when one of the following is detected - serial GC used on a multi-core machine, parallel GC on a single-core machine, more GC threads were configured than available cores, or a parallel GC was configured to run in 1 thread
+    - name: Duplicated Flags
+      severity: Info
+      description: Triggers if duplicate flags were provided to the runtime (e.g. `-Xmx2g -Xmx5g`). This is a problem as it may lead to changes not having the expected effect.
+    - name: Options
+      severity: Warn
+      description: Triggers if undocumented, deprecated or non-recommended option flags were detected.
+    - name: Stackdepth Setting
+      severity: Warn
+      description: Triggers if events were found with truncated stacktraces which may make it hard to understand profiling data.
+    - name: VMOperation Peak Duration
+      severity: Warn
+      description: Triggers if a blocking VM operation (or combination of ops close in time) taking more than 2 seconds. Reports details about the operation with the highest duration.
+    - name: GC Pauses
+      severity: Warn
+      description: Triggers if more than 10% of time was spent in GC pauses.
+    - name: GC Pause Peak Duration
+      severity: Info
+      description: Triggers if at least one GC pause took more than 1 second.
+    - name: Deadlocked Threads
+      severity: Warn
+      description: Triggers if we see a custom datadog event capturing deadlocked threads during the profile.
+    - name: Deadlocked Threads Detected
+      severity: Warn
+      description: Triggers if max number of deadlocked threads over query context is bigger than 0.
+    - name: Thrown Exceptions
+      severity: Warn
+      description: Triggers when the rate of thrown (caught and uncaught) exceptions per minute goes above a threshold (defauls to 10K)
+    - name: Primitive Value Boxing
+      severity: Info
+      description: Triggers if more than 5% of CPU time was spent doing primitive<>object value conversions.
+    - name: Explicit GC
+      severity: Info
+      description: Triggers if there are System.gc() calls.
+    - name: Head of line blocking
+      severity: Info
+      description: Triggers if a queue event gets stuck behind the given activity.
+---
+
+## Overview
+Automated Analysis helps teams detect and troubleshoot problems faster, without requiring deep expertise in code profiling. Powered by Continuous Profiler, Automated Analysis continuously monitors your applications and surfaces critical issues in real time, along with actionable insights to guide resolution. When a problem is detected, Automated Analysis provides:
+
+- A high-level summary explaining the issue and why it matters
+- Contextual insights from profiling data (e.g., affected methods, packages, or processes)
+- Recommended next steps to help you resolve the issue efficiently
+
+By reducing the expertise required to take action, Automated Analysis enables faster resolution of performance issues, increases product adoption, and helps teams avoid costly blind spots. It also lays the foundation for powering performance and cost insights across the Datadog platform.
path: content/en/profiler/automated_analysis.md
user: login: brantigua
body: added this on my end!
created_at: 2025-05-19T17:18:53Z
author_association: CONTRIBUTOR

PR comments:
user: login: github-actions[bot]
created_at: 2025-05-16T21:17:23Z
body: ## Preview links (active after the `build_preview` check completes)

### New or renamed files
* https://docs-staging.datadoghq.com/bryan.antigua/automated-analysis/profiler/automated_analysis



### Modified Files
* https://docs-staging.datadoghq.com/bryan.antigua/automated-analysis/profiler/connect_traces_and_profiles
author_association: CONTRIBUTOR
user: login: janine-c
created_at: 2025-05-16T22:10:44Z
body: Created DOCS-10940 for editorial review 🙂 
author_association: CONTRIBUTOR
user: login: brantigua
created_at: 2025-05-19T20:49:11Z
body: /merge
author_association: CONTRIBUTOR
user: login: dd-devflow[bot]
created_at: 2025-05-19T20:49:15Z
body: <!-- "FeedbackWorkflowId":"e8737029-66d4-4e38-a878-8f3c791f76ff_36" -->
[View all feedbacks in Devflow UI.](https://mosaic.us1.ddbuild.io/devflow/logs/e8737029-66d4-4e38-a878-8f3c791f76ff_36)

`2025-05-19 20:49:15 UTC` :information_source: Start processing command `/merge`

---
`2025-05-19 20:49:24 UTC` :information_source: **MergeQueue:** waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
**Note:** if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with `/remove` command.

---
`2025-05-19 20:51:16 UTC` :information_source: **MergeQueue:** merge request added to the queue

The expected merge time in `master` is approximately 21m (p90).

---
`2025-05-19 21:10:07 UTC` :information_source: **MergeQueue:** This merge request was merged

author_association: NONE