<?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>Logging on Shubham Singh</title>
    <link>https://1shubham7.blog/tags/logging/</link>
    <description>Recent content in Logging on Shubham Singh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://1shubham7.blog/tags/logging/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Log Collectors Collect and Label Your Logs</title>
      <link>https://1shubham7.blog/log-collection-and-labels/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/log-collection-and-labels/</guid>
      <description>A container log line on disk contains no idea which pod wrote it. Everything you filter by later is constructed by the collector at collection time. What the file actually looks like, how collectors find it, where every label comes from, and why that design decides the health of your logging stack.</description>
    </item>
    
    <item>
      <title>Ten Things to Get Right Before You Run Loki in Production</title>
      <link>https://1shubham7.blog/loki-production-checklist/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/loki-production-checklist/</guid>
      <description>Deployment mode, object storage, label cardinality, multi-tenancy and auth, cross-cluster shipping, and the failures that are silent rather than loud. Written after moving a Loki install twice and debugging an object store that corrupted everything it was given.</description>
    </item>
    
  </channel>
</rss>
