<?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>Vector on GnTech Blog</title>
    <link>https://blog.gntech.me/tags/vector/</link>
    <description>Recent content in Vector on GnTech Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Nov 2026 00:00:00 -0400</lastBuildDate>
    <atom:link href="https://blog.gntech.me/tags/vector/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Test What Happens to Your Logs During a Destination Outage</title>
      <link>https://blog.gntech.me/posts/2026-11-10-test-log-delivery-during-destination-outage/</link>
      <pubDate>Tue, 10 Nov 2026 00:00:00 -0400</pubDate>
      <guid>https://blog.gntech.me/posts/2026-11-10-test-log-delivery-during-destination-outage/</guid>
      <description>Make a local receiver return HTTP 503, let Vector retry, and measure which numbered events reach the destination after recovery.</description>
    </item>
    <item>
      <title>Did Your Log Shipper Keep Reading After Rotation?</title>
      <link>https://blog.gntech.me/posts/2026-11-09-verify-log-shipper-after-rotation/</link>
      <pubDate>Mon, 09 Nov 2026 12:00:00 -0400</pubDate>
      <guid>https://blog.gntech.me/posts/2026-11-09-verify-log-shipper-after-rotation/</guid>
      <description>Use Vector and a local JSON Lines sink to check for missing or duplicated events across a log rename and a clean collector restart.</description>
    </item>
  </channel>
</rss>
