yCrash has introduced an audit trail feature, addressing enterprise security gaps by logging user actions. This enhancement enables tracking of who accesses sensitive production data, ensuring compliance and accountability. With SSO integration, the logs provide detailed user activity, fostering a culture of security awareness among engineers and improving overall troubleshooting security.
Visualising JVM Metrics Using Prometheus and Grafana
This article provides a comprehensive guide for visualizing Java Virtual Machine (JVM) metrics using Prometheus and Grafana. It explains how to set up the monitoring system, retrieve JVM metrics from applications, and create custom dashboards. The integration enhances problem detection and facilitates quicker resolution, boosting application performance and reliability.
The Manager’s guide to Memory Analysis: Bridging the Gap between Dev and Ops
The development and operations teams must collaborate effectively to address memory analysis in applications, as it significantly affects performance and customer satisfaction. Tools like yCrash facilitate this by providing insights into memory use, facilitating root cause analysis, and aligning both teams, ultimately enhancing system performance and ROI.
JVM Optimization in Real Systems
A Spring Boot application unexpectedly surged in JVM memory usage from 8GB to 61GB without any deployment or configuration changes. By diagnosing a ZipFile$Source memory leak with yCrash, the team identified excessive caching leading to the leak. By disabling caching and restarting the app, they reduced memory usage to 4GB effectively.
‘Advanced Heap Dump Analysis Techniques’ Webinar
In September, a webinar titled “Advanced Heap Dump Analysis Techniques” gathered developers and JVM enthusiasts to discuss efficient strategies for analyzing memory issues through heap dumps. Topics covered included querying with OQL, using APIs for automation, and correlating data to quickly identify memory leaks, ultimately promoting healthier Java applications.
‘Matchmaking for JVMs: How to Pick the Perfect GC Partner’ Webinar
In August, a webinar titled "Matchmaking for JVMs: How to Pick the Perfect GC Partner" focused on selecting optimal Garbage Collector (GC) algorithms for Java performance. It highlighted various GC types, their trade-offs, and provided practical strategies, metrics for evaluation, and real-world examples to enhance application performance.
‘What to Capture When It Breaks: 16 Artifacts That Reveal Root Causes’ Webinar
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 Hidden Battle: Troubleshooting Issues in On-Prem Customer Deployments’ webinar
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.
‘Micro-Metrics Every Performance Engineer Should Validate Before Sign-Off’ webinar
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.
Best Practices for Capturing the Micro-Metrics Labs Often Miss
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.
