You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
JCT is a Java agent that records real method call stacks while your application is running.
4
4
5
-
If you work in a legacy app and ask things like "Can we remove this?" or "Is this code path still hit in production-like traffic?", JCT gives you hard runtime evidence instead of guesses.
5
+
If you work in a legacy app and ask things like "Can we remove this?" or "Is this code path still hit in production traffic?", JCT gives you hard runtime evidence instead of guesses.
6
6
7
7
## Table of Contents
8
8
@@ -146,6 +146,7 @@ JCT currently ships with three output processors.
146
146
- Writes one JSON event per line into a daily log file (`jct_yyyy_dd_MM.log`) in `processor.stackFolderName`
147
147
- Best when you want the simplest setup, local debugging, or offline analysis
148
148
- Trade-off: local disk I/O and file handling are on you
149
+
- Hint: captured traces can get very large on busy systems, so filesystem usage can grow quickly
0 commit comments