{"repo":"niesfisch/java-code-tracer","free":true,"listed":false,"github":"https://github.com/niesfisch/java-code-tracer","clone":"git clone https://github.com/niesfisch/java-code-tracer.git","description":"JCT is a call graph generator that works via byte code instrumentation. it records the flow through your application to gather call statistics. It helps to analyze which code is still used in production and which code can be removed (e.g. for big monolithic legacy applications)","language":"Java","stars":25,"topics":["java","profile","tracer","javaagent","jdk","jre","legacy","stacktrace","stack","callgraph"],"license":"MIT","category":"analytics","readme_excerpt":"Java Code Tracer (JCT) JCT is a Java agent that records real method call stacks while your application is running. 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. Table of Contents - Why This Is Useful in Legacy Systems - What JCT Does at Runtime - Quick Start in 3 Steps - Recommended Local Workflow: ELK - Alternative Stack: ClickHouse + Vector + Grafana - ELK vs. ClickHouse — When to Choose Which - Project Status - Java Version - Build - Configure - Class Include/Exclude Patterns - Hard-Skipped Packages (Non-Overridable) - Run an Application with JCT - Available Processors - Stack Volume Control (All vs New Stacks) - Message Format - Logging - Hello World Walkthrough - Tools - ELK Integration Guide - Sample Application Screenshots - Similar Projects - IntelliJ JVM Options Example - License Why This Is Useful in Legacy Systems In older monoliths and large shared platforms, static code search is usually not enough. - Feature flags, reflection, and framework magic hide real call paths - \"Unused\" code often turns out to be used by one weird but critical flow - Refactoring without runtime traces is risky and slow JCT helps you reduce that risk by showing what was actually executed. What JCT Does at Runtime When you attach JCT via -javaagent , it does this: 1. Instruments methods that match your include/exclude config 2. Captures call stacks during","default_branch":null,"files":null,"tree":[],"storefront":"/r/niesfisch","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/niesfisch/java-code-tracer/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}