Application logs are crucial for engineers to troubleshoot production incidents, but manual inspection is often inefficient. The 'yCrash Log' tool utilizes AI and ML to analyze and structure unfiltered log data, identify errors, and provide solutions, improving incident response time and system reliability. It enhances traditional log management by automating root cause analysis.
February 11, 2026
yCrash Buddy is an AI Troubleshooting assistant aimed at enhancing team efficiency by tenfold. It analyzes incident reports and artifact dumps, providing interpretable insights and actionable recommendations. Upcoming features include autonomous troubleshooting, intelligent execution of engineer instructions, and automated performance testing. Available in Cloud and On-Prem editions, it requires a license for activation.
October 10, 2025
Last week, I traveled from San Francisco to London for a keynote on Java performance issues, then visited NHS Scotland in Dundee. I appreciated their efficiency in adopting our yCrash tool. Productive meetings about .NET support led to planned releases in early 2026. Scotland's hospitality and culture left a lasting impression.
October 6, 2025
Troubleshooting on-premise application issues is complicated due to limited access to customer systems and reliance on their support staff for vital diagnostic data. Challenges include incomplete information, security concerns, miscommunication, and environmental instabilities. Implementing the yc-360 Script can streamline artifact collection, improving diagnosis and reducing resolution times.
June 18, 2025
The post addresses challenges faced in performance testing, including discrepancies between test and production environments, reliance on synthetic data, and the absence of long-running tests. To improve detection of performance issues, it suggests enhancing testing with Micro-Metrics, implementing chaos engineering, and recording production traffic for realistic simulations.
June 2, 2025
To accurately forecast production performance issues, validating Micro-Metrics is essential. Key best practices include enabling Garbage Collection Logs, triggering 'yc-360 Script' midway and at the end of tests, and utilizing self-trigger M3 mode for endurance tests. Comparing new and previous baseline incident reports helps identify performance degradation trends effectively.
June 2, 2025
