<?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>Observability on &lt;shortdiv /&gt;</title>
    <link>https://shortdiv.com/tags/observability/</link>
    <description>Recent content in Observability on &lt;shortdiv /&gt;</description>
    <generator>Hugo -- 0.152.0</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Nov 2026 16:37:51 -0500</lastBuildDate>
    <atom:link href="https://shortdiv.com/tags/observability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Journey to Otel Collector</title>
      <link>https://shortdiv.com/posts/the-journey-to-otel-collector/</link>
      <pubDate>Fri, 19 Dec 2025 23:25:03 -0500</pubDate>
      <guid>https://shortdiv.com/posts/the-journey-to-otel-collector/</guid>
      <description>&lt;p&gt;In a previous role, I worked on establishing an observability stack using OpenTelemetry (OTel) which mostly involved setting up instances of OTel collector to run across a distributed network. The main goal of this effort was to decouple data collection from data export, to more reliably gather data from various services for export.&lt;/p&gt;
&lt;p&gt;In the simplest of setups, logs, and metrics can be sent directly to Grafana Cloud via an &lt;strong&gt;OTLP (OTel Protocol)&lt;/strong&gt; exporter. An OTLP exporter is the component that sends your telemetry data from the OTel Collector to a backend like Grafana. Exporters generally handle authentication, and batching and can be configured for HTTP or gRPC transport. Essentially, they act as the bridge between your application’s telemetry and your monitoring platform.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
