docs: Don't mention runtime guest kernel CLI for agent tracing

Remove the example showing how to set the trace mode in the runtime's configuration file. The reason for doing this being that the plan is for the runtime to control adding such guest kernel command line options as part of kata-containers/runtime#1369. Signed-off-by: James O. D. Hunt <[email protected]>
kata-containers · Mar 18, 2019 · f64fe3c · f64fe3c
1 parent 58fcce0
commit f64fe3c
Showing 1 changed file with 1 addition and 8 deletions.
diff --git a/TRACING.md b/TRACING.md
@@ -127,7 +127,7 @@ Call the gRPC `StartTracing()` API to start tracing and the corresponding `StopT
 ## Enabling static tracing
 
 Static tracing is enabled by adding the `agent.trace` option in the
-`kernel_params=` variable in the runtime's `configuration.toml` file.
+guest kernels command line.
 
 ### Static tracing options
 
@@ -139,13 +139,6 @@ following:
 | "isolated" | `agent.trace=isolated` (or just `agent.trace`) |
 | "collated" | `agent.trace=collated` |
 
-For example, to enable isolated tracing explicitly, add the following to the
-runtime's `configuration.toml` file:
-
-```
-kernel_params = "agent.trace=isolated ... "
-```
-
 > **Note:**
 >
 > Agent tracing is separate from the tracing for other Kata Containers