When applications are deployed in customer-managed environments, resolving performance issues becomes a hidden battle. Limited access to logs, delayed responses, and vague problem descriptions make root cause analysis incredibly challenging. In this presentation, we walk through: The six most common hurdles faced in on-prem troubleshooting A practical 360° artifact collection strategy using the open-source yc-360 script Real-world case studies covering transaction timeouts, CPU spikes, and intermittent HTTP 502 errors Benefits of structured data capture in reducing investigation time and improving communication with customers ✅ Whether you're supporting enterprise clients or building tools for distributed environments, this deck offers a practical roadmap to make on-prem issue resolution faster and less frustrating.

2. 2
Challenges in Troubleshooting On-Prem Applications
1. Missing
Troubleshooting
Artifacts
2. Reliance on Customer Staff
for Timely Data Collection
3. Refusal to Share
Artifacts for Security
Concerns
4. Environmental Instability
& Hidden Customizations
5. Misleading Communication
About Problems
6. Unable to Reproduce
Problem Internally

3. Open-Source script:
https://github.com/ycrash/yc-360-script
5. GC Log
10. netstat
12. vmstat
2. Thread Dump
9. dmesg
3. Heap Dump
13. ps
15. Disk Usage
7. top
6. Extended Data
11. ping
14. Kernel Params
1. App Logs
16. metadata
4. Heap Substitute 8. top -H
3
Effective Troubleshooting Strategy: 360° Artifacts
./yc –p <PROCESS_ID>

4. 4
Key Features of yc-360 Script
1. Platform Agnostic 2. Pristine Data Capture 3. Extended Data
Capturing
4. Security and Compliance 5. Almost zero Overhead 6. Completes under 30
seconds
https://docs.ycrash.io/yc-360/en
vironment/introduction.html
https://docs.ycrash.io/yc-360/fe
atures/pristine-capture.html
https://docs.ycrash.io/yc-360/feat
ures/extended-data.html
https://docs.ycrash.io/ycrash-featur
es/secure-troubleshooting.html
https://blog.ycrash.io/ycrash-age
nt-overhead-performance/
https://blog.ycrash.io/ycrash-age
nt-overhead-performance/

5. 5
360° Analysis Demo
https://docs.ycrash.io/ycrash-features/bundle-upload.html

6. 6
Case Study 1: Transaction Timeout
https://blog.gceasy.io/java-gc-tuning-improved-insurance-company-throughput/

7. 7
Case Study 2: CPU Spike
https://blog.gceasy.io/java-gc-tuning-improved-insurance-company-throughput/

8. 8
Case Study 3: Intermittent HTTP 502 Errors
https://blog.gceasy.io/java-gc-tuning-improved-insurance-company-throughput/

9. EBS Architecture
9

10. Clue: Nginx Error
10

11. 1. GC Log
10. netstat
12. vmstat
2. Thread Dump
9. dmesg
3. Heap Dump
6. ps
8. Disk Usage
5. top 13. iostat
11. ping
14. Kernel Params
15. App Logs
16. metadata
4. Heap Substitute
7. top -H
11
360° Data
Open-Source script:
https://github.com/ycrash/yc-360-script

12. 12

13. 13
Benefits of 360° Artifacts
1. Simplifies the root cause
identification process
2. Minimizes Friction with
Customer

14. Thank you, my friends!
Ram Lakshmanan
@ycrash_rca
This deck will be published in: https://blog.ycrash.io
https://www.linkedin.com/company/ycrash