<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Raj Nishtala on Medium]]></title>
        <description><![CDATA[Stories by Raj Nishtala on Medium]]></description>
        <link>https://medium.com/@raj.nishtala?source=rss-17ddd309d384------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*A8Jkown3uHVlXPPJ</url>
            <title>Stories by Raj Nishtala on Medium</title>
            <link>https://medium.com/@raj.nishtala?source=rss-17ddd309d384------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:33:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@raj.nishtala/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OpenTelemetry for Observability]]></title>
            <link>https://medium.com/@raj.nishtala/opentelemetry-for-observability-b2ec209e1bff?source=rss-17ddd309d384------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2ec209e1bff</guid>
            <category><![CDATA[opentelemetry]]></category>
            <category><![CDATA[observability]]></category>
            <dc:creator><![CDATA[Raj Nishtala]]></dc:creator>
            <pubDate>Fri, 21 Jan 2022 11:37:02 GMT</pubDate>
            <atom:updated>2022-01-21T11:37:02.671Z</atom:updated>
            <content:encoded><![CDATA[<h3>Observability</h3><p>In software, <a href="https://lightstep.com/observability/">observability</a> generally refers to the ability to understand an application’s behavior and performance based only on its telemetry. Put more simply, observability is what allows you to understand what’s happening in production <em>without changing your code</em>.</p><p>In distributed systems, this telemetry can be divided into three overarching flavors:</p><ul><li>(Distributed) Traces: detailed records of the paths that distinct requests take as they propagate across an entire system (including across service boundaries)</li><li>Metrics: aggregate statistics (mostly counters and gauges) about processes and infrastructure, typically with key:value tags attached to disaggregate patterns</li><li>Logs: timestamped messages — sometimes structured — emitted by services or other components (though, unlike traces, not necessarily associated with any particular user request or transaction)</li></ul><p><strong>OpenTelemetry is the first step in any observability strategy</strong>, vendor-neutral data is a great starting point.</p><h3>OpenTelemetry</h3><p>OpenTelemetry, the project provides a single set of language-specific APIs, SDKs, agents, and other components that you can use to collect distributed traces, metrics, and related metadata from your applications. In addition to its core capabilities, much of OpenTelemetry’s utility comes from integrations for HTTP and RPC libraries, storage clients, etc. that allow developers to capture critical observability data from their applications with almost zero effort. After capturing these signals, each OpenTelemetry component can export them to your backends of choice, including <strong>Prometheus</strong>, Jaeger, Zipkin, Azure Monitor, Dynatrace, Google Cloud Monitoring + Trace, Honeycomb, Lightstep, New Relic, and Splunk.</p><p>When a library or integration calls into OpenTelemetry, this is what the telemetry delivery pipeline looks like:</p><ul><li><strong>API</strong> is used to instrument a library</li><li><strong>SDK</strong> to send telemetry into <strong>Processing </strong>and <strong>Exporting </strong>pipeline</li><li>Out of the process <strong>Collector </strong>is used for data filtering, aggregation and batching</li><li><strong>Exporter </strong>sends telemetry to the backend of your choice.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s1sQ2Y9TO6NwHqynup8uog.png" /><figcaption>opentelemetry pipeline</figcaption></figure><h3>Exporter</h3><p>The OpenTelemetry component responsible for batching and transporting telemetry data to a backend system is known as an exporter. The exporter interface is implemented by the OpenTelemetry SDKs, and uses a simple plug-in model that allows for telemetry data to be translated to the particular format a backend system requires. Examples of OpenTelemetry exporters can be found below:</p><p><a href="https://opentelemetry.io/docs/instrumentation/js/exporters/">Exporters</a></p><h3>The Collector</h3><p>The Collector is a separate process that is designed to be a ‘sink’ for telemetry data emitted by many processes, which can then export that data to backend systems. The Collector has two different deployment strategies — either running as an agent alongside a service, or as a remote application. In general, using both is recommended: the agent would be deployed with your service and run as a separate process or in a sidecar; meanwhile, the collector would be deployed separately, as its own application running in a container or virtual machine. Each agent would forward telemetry data to the Collector, which could then export it to a backend analytics system as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*k8u3cYHHK2jSJE3G7nfEag.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2ec209e1bff" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>