wu-sheng commented on code in PR #12671:
URL: https://github.com/apache/skywalking/pull/12671#discussion_r1824547585


##########
docs/en/setup/backend/backend-async-profiler.md:
##########
@@ -0,0 +1,85 @@
+`# Async Profiler
+
+Async Profiler is bound within the auto-instrument agent and corresponds to 
[In-Process 
Profiling](../../concepts-and-designs/profiling.md#in-process-profiling).
+
+It is passed to the proxy in the form of a task, allowing it to be enabled or 
disabled dynamically.
+When service encounters performance issues (cpu usage, memory allocation, 
locks), async-profiler task can be created.
+When the proxy receives a task, it enables Async Profiler for sampling.
+After sampling is completed, a flame graph will be generated for performance 
analysis to determine the specific business code line that caused the 
performance problem.
+
+## Active in the OAP
+OAP and the agent use a brand-new protocol to exchange Async Profiler data, so 
it is necessary to start OAP with the following configuration:
+
+```yaml
+receiver-async-profiler:
+  selector: ${SW_RECEIVER_ASYNC_PROFILER:default}
+  default:
+```
+
+## Async Profiler Task with Analysis
+
+To use the Async Profiler feature, please follow these steps:
+
+1. **Create Async Profiler task**: Use the UI or CLI tool to create a task.
+2. **Wait agent collect data and upload**: Wait for Async Profiler to collect 
JFR data and report
+3. **Query task progress**: Query the progress of tasks, including analyzing 
successful and failed instances and task logs
+4. **Analyze the data**: Analyze the JFR data to determine where performance 
bottlenecks exist in the service.
+
+### Create Async Profiler task

Review Comment:
   ```suggestion
   ### Create an Async Profiler task
   ```



##########
docs/en/setup/backend/backend-async-profiler.md:
##########
@@ -0,0 +1,85 @@
+`# Async Profiler

Review Comment:
   ```suggestion
   # Async Profiler
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to