The webinar “What to Capture When It Breaks” focused on critical data collection during production incidents, showcasing 16 essential artifacts like GC logs and OS metrics. It emphasized a structured approach for root cause analysis, providing engineers with tools, guidelines, and real-world examples to enhance incident response and minimize downtime.
The webinar addressed native memory leaks in Java applications, a challenging issue often overlooked by developers. It covered the allocation and leakage of native memory, common sources of leaks, and practical methods for detection, analysis, and resolution. The session aimed to equip participants with the tools necessary to address these critical performance problems.
The recent webinar focused on troubleshooting performance issues in customer-managed, on-premise environments. Experts discussed challenges like limited visibility and communication delays, emphasizing the need for essential artifacts for diagnosis. Participants learned practical strategies, including automation workflows and effective communication techniques, to enhance resolution accuracy and reduce turnaround times.
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.
The June webinar focused on performance testing, emphasizing the importance of micro-metrics like garbage collection behavior, object creation rates, and thread patterns. These critical indicators can reveal potential issues before they escalate. Participants learned strategies to enhance JVM performance validation and reduce post-deployment problems, highlighting that macro-metrics alone are insufficient.
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.
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.
Missed our May webinar on Not So Common Memory Leaks in Java? We uncovered subtle yet serious memory issues—like thread local leaks, inner class traps, and framework-related memory retention—that often go undetected in Java applications. This session walked through advanced heap analysis, profiling techniques, and real-world fixes to help you tackle elusive leaks and boost performance.
In April, a webinar focused on memory leaks in Java revealed their impact on application performance, particularly in long-running systems. It explored common leak patterns, detection techniques, and solutions. Attendees gained insights into tools for diagnosing issues and actionable strategies for resolving memory leaks, enhancing JVM behavior and application stability.
We recently hosted a webinar on how micro-metrics can help detect performance issues before they cause outages. While traditional metrics often miss hidden problems, experts shared 7 key micro-metrics that can spot early signs of issues like memory leaks and CPU spikes. The session also covered real-world examples and practical tips for preventing performance failures.
