blob: bd2c82e075254d0cb4455609c91237baf9571f36 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
# TODO's
* Target OS is Rocky 9 and not Rocky 8 (can use a bhyve VM)
* More filters
* By directory
* By directory sub-match
* By regex match of whole path
* By syscall
* Output format so that it is compatible with the flamegraph grapher
* Capture more tracepoints? See comments in tracepoints.c's header.
* Automatic testing (integration tests)
* Performance benchmark...
## FlameGraphs
What format? What to visualize on the stack axis?
```
user;cmd_name;pid;tid;syscall_name count
user;cmd_name;pid;tid;syscall_name bytes
user:cmd_name;pid:tid;prev_syscall_name->syscall_name;duration IN DIFFERENT COLOR
user:cmd_name;pid:tid;prev_syscall_name->syscall_name;fd;duration IN DIFFERENT COLOR
user;cmd_name;pid;tid;syscall_name duration
user;cmd_name;pid;tid;syscall_name;fd duration
user;cmd_name;pid;tid;PATHMATCH;syscall_name duration
user;cmd_name;pid;tid;OTHER;syscall_name duration
```
`pathdecoded`? Maybe:
* By directory
* By mountpoint
* By device
Consider:
* File base path or mount point or device name
* Filename?
* Time spent between syscalls?
|
