Added new page for automated analysis, as well as screenshots

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

content/en/profiler/automated_analysis.md

@@ -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
+<!-- The table below is auto-generated. Add new entries in multifiltersearch with new insights as they become available. -->
+{{< multifilter-search >}} 
+
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://app.datadoghq.com/profiling/explorer
+

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]: https://www.datadoghq.com//profiler/automated_analysis/
 
 Depending on the runtime and language, the lanes vary: