1# One buffer allocated within the central tracing binary for the entire trace, 2# shared by the two data sources below. 3buffers { 4 size_kb: 20480 5 fill_policy: DISCARD 6} 7 8# Ftrace data from the kernel, mainly the process scheduling events. 9data_sources { 10 config { 11 name: "linux.ftrace" 12 target_buffer: 0 13 ftrace_config { 14 ftrace_events: "sched_switch" 15 ftrace_events: "sched_waking" 16 ftrace_events: "sched_wakeup_new" 17 18 ftrace_events: "task_newtask" 19 ftrace_events: "task_rename" 20 21 ftrace_events: "sched_process_exec" 22 ftrace_events: "sched_process_exit" 23 ftrace_events: "sched_process_fork" 24 ftrace_events: "sched_process_free" 25 ftrace_events: "sched_process_hang" 26 ftrace_events: "sched_process_wait" 27 } 28 } 29} 30 31# Resolve process commandlines and parent/child relationships, to better 32# interpret the ftrace events, which are in terms of pids. 33data_sources { 34 config { 35 name: "linux.process_stats" 36 target_buffer: 0 37 } 38} 39 40# 10s trace, but can be stopped prematurely. 41duration_ms: 10000 42