<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Devops on 1Stop</title><link>https://blogs.rameskum.com/tags/devops/</link><description>Recent content in Devops on 1Stop</description><image><title>1Stop</title><url>https://blogs.rameskum.com/images/og-default.png</url><link>https://blogs.rameskum.com/images/og-default.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 22 Sep 2026 09:10:00 -0400</lastBuildDate><atom:link href="https://blogs.rameskum.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>The 3 A.M. Toolkit: Unix One-Liners for Triaging a Dying Java Service</title><link>https://blogs.rameskum.com/posts/java-service-triage-unix-toolkit/</link><pubDate>Tue, 22 Sep 2026 09:10:00 -0400</pubDate><guid>https://blogs.rameskum.com/posts/java-service-triage-unix-toolkit/</guid><description>It&amp;#39;s 3 A.M., PagerDuty is screaming, and your Java service is dying. The triage ladder that actually works: box first, then logs, then thread dumps, then GC — with the exact grep/awk/jq/jstack one-liners for each step, realistic sample output, and a 60-second triage script you can steal.</description></item></channel></rss>