<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Chenna Vemula</title>
    <description>The latest articles on DEV Community by Chenna Vemula (@cvemula1).</description>
    <link>https://dev.to/cvemula1</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3826006%2F4fd40f4d-9a10-4636-9f94-ee18e6aecae3.jpeg</url>
      <title>DEV Community: Chenna Vemula</title>
      <link>https://dev.to/cvemula1</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cvemula1"/>
    <language>en</language>
    <item>
      <title>ChangeTrail – Open-source unified change timeline for incident response</title>
      <dc:creator>Chenna Vemula</dc:creator>
      <pubDate>Sun, 15 Mar 2026 23:11:13 +0000</pubDate>
      <link>https://dev.to/cvemula1/changetrail-open-source-unified-change-timeline-for-incident-response-1d3i</link>
      <guid>https://dev.to/cvemula1/changetrail-open-source-unified-change-timeline-for-incident-response-1d3i</guid>
      <description>&lt;p&gt;I built this because every on-call incident starts with "what changed?" &lt;br&gt;
and I'd spend 20 minutes jumping between Kubernetes, GitHub, and AWS &lt;br&gt;
dashboards to figure it out.&lt;/p&gt;

&lt;p&gt;ChangeTrail collects changes from all those sources and shows them on &lt;br&gt;
one timeline. You can try it in 60 seconds:&lt;/p&gt;

&lt;p&gt;git clone &lt;a href="https://github.com/cvemula1/ChangeTrail.git" rel="noopener noreferrer"&gt;https://github.com/cvemula1/ChangeTrail.git&lt;/a&gt; &amp;amp;&amp;amp; cd ChangeTrail &amp;amp;&amp;amp; make up&lt;/p&gt;

&lt;p&gt;It's Python/FastAPI + React, runs fully self-hosted with Docker Compose. &lt;br&gt;
MIT licensed. Currently supports Kubernetes and GitHub, with ArgoCD and &lt;br&gt;
Terraform collectors as good-first-issues for contributors.&lt;/p&gt;

&lt;p&gt;Would love feedback on the approach and what sources to prioritize next.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>python</category>
      <category>devops</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
