flamegraphs and live debugging

src/content/docs/auto-telemetry-pixie/get-started-auto-telemetry-pixie.mdx

@@ -22,8 +22,9 @@ Simply put, Auto-telemetry with Pixie offers the quickest option for getting obs
 
 Our Pixie integration gives you the best of both worlds: Pixie’s fast and simple Kubernetes observability coupled with New Relic One’s incident correlation, intelligent alerting, and long-term retention. 
 
-You’ll get visibility into HTTP services using golden signals, HTTP transactions, database transactions, distributed tracing, and JVM metrics. You can operate, debug, and scale your Kubernetes clusters based on the information you learn about how your clusters and services are running. Using the New Relic [Explorer](/docs/new-relic-one/use-new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/), you can see key metrics and events at every level, starting with the cluster, and diving down into namespaces, deployments, and pods. You can quickly spot anomalous behavior, and where it’s happening. If you need further insight, you can easily link over to Pixie's native UI for advanced debugging with PXL scripts. 
+You’ll get visibility into HTTP services using golden signals, HTTP transactions, database transactions, distributed tracing, and JVM metrics. You can operate, debug, and scale your Kubernetes clusters based on the information you learn about how your clusters and services are running. Using the New Relic [Explorer](/docs/new-relic-one/use-new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/), you can see key metrics and events at every level, starting with the cluster, and diving down into namespaces, deployments, and pods. You can quickly spot anomalous behavior, and where it’s happening. 
 
+And dive deeper using embedded visualizations of your Pixie data. Quickly identify hot spots with [Flamegraph](#flamegraph). On the [Live debugging with Pixie tab](#live-debugging), answer questions like what SQL requests your app is making or which services are talking to each other. 
 
 ## Install Auto-telemetry with Pixie
 
@@ -85,8 +86,24 @@ In the cluster explorer, you can get a quick overview of the nodes in your clust
 Containers might be listed for up to four hours after they get decommissioned. 
 </Callout>
 
-You can query the Pixie data that's available in New Relic One and create dashboards for at-a-glance monitoring. Find the data model and sample queries [here](/docs/integrations/kubernetes-integration/understand-use-data/auto-telemetry-pixie-data-model).
+You can query the Pixie data in New Relic One and create dashboards for at-a-glance monitoring. Find the data model and sample queries [here](/docs/integrations/kubernetes-integration/understand-use-data/auto-telemetry-pixie-data-model).
+
+## Investigate usage spikes with Flamegraph [#flamegraph]
+
+Debugging is orders of magnitude easier when you can quickly see what your application is doing. Flamegraph, a Pixie always-on visualization, requires no instrumentation, redeploying, or recompiling. It works for compiled languages - Go, C+, Rust, to name a few. Flamegraph tells you in a glance what functions your application is spending time on, and where you have hot spots. Flamegraph is especially useful for hierarchical resource use, like disk usage and CPU utilization. For more information on how to read Flamegraph, see [the Pixie documentation](https://docs.pixielabs.ai/tutorials/profiler#reading-the-flamegraph). 
+
+
+## Live debugging with Pixie [#live-debugging]
+
+On the **Live debugging with Pixie** tab, run PxL scripts -- scripts written in Pixie's PxL language -- to view live data captured through eBPF. Select the **script** drop-down and select a script to run in the tab. Scripts enable you to debug: 
+
+* Traffic in multiple formats: HTTP and HTTPs (including encrypted), DNS, Postgres, MySQL, Cassandra, Redis (currently supporting SQL and HTTP in beta)
+* Kubernetes services and their throughput, error rate, and latency statistics
+* Service maps to learn which services are talking to each other
+* Network traffic maps to learn which nodes are talking to each other
+* JVM data
+
+If you don't find the script you need, you can [write your own PxL scripts](https://docs.pixielabs.ai/tutorials/pxl-scripts/).
+Find more information about available scripts in [Pixie's open source repo](https://github.com/pixie-labs/pixie/tree/main/src/pxl_scripts/px).
 
-In addition to analyzing the performance of your clusters in New Relic One, you might want to use Pixie's advanced debugging workflows. In Pixie's native UI, you can drill down further into header and content requests. Click **Explore service in Pixie** to see information about your service in the Pixie UI. Learn more about [writing PXL scripts in the Pixie docs](https://docs.pixielabs.ai/tutorials/pxl-scripts/).
 
-## Live debugging [#live-debugging]