<?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>Artificial-Intelligence on Akshay Deshpande</title>
    <link>https://akshayd-dev.pages.dev/tags/artificial-intelligence/</link>
    <description>Recent content in Artificial-Intelligence on Akshay Deshpande</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://akshayd-dev.pages.dev/tags/artificial-intelligence/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Metrics Types - When to use what ?</title>
      <link>https://akshayd-dev.pages.dev/posts/metrics-types-when-to-use-what/</link>
      <pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/metrics-types-when-to-use-what/</guid>
      <description>&lt;p&gt;This writeup talks about different metric type that an application can emit as telemetry. It intends to cover the case of when to use which metric types and the usecase for them.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://akshayd-dev.pages.dev/posts/metrics-types-when-to-use-what/images/image.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Metrics is one of the oldest forms of telemetry. There are many APM solutions, whose billing model runs on the number of metrics you send to them. But it is often not clear to app devs on what kind of metrics to emit from applications. Infact, the types of metrics can be confusing sometimes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>When to Emit What O11y Signal?</title>
      <link>https://akshayd-dev.pages.dev/posts/when-to-emit-what-o11y-signal/</link>
      <pubDate>Thu, 04 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/when-to-emit-what-o11y-signal/</guid>
      <description>&lt;p&gt;The intention of this page is to put together the &lt;em&gt;Observability Signal Guidelines&lt;/em&gt; which will provide the required visibility into the systems without hurting the cost aspect of the solution.&lt;/p&gt;
&lt;p&gt;Three basic observability signals that any application emits are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Metrics,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Traces and&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Logs&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The general question is - &lt;em&gt;&lt;strong&gt;When to emit what signal?&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The answer lies in the &lt;em&gt;intent&lt;/em&gt; behind the signal being emitted. &lt;em&gt;&lt;strong&gt;What do you intend to measure with the Observability signal that you are emitting?&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Enhancing Observability with OTel Custom Processors</title>
      <link>https://akshayd-dev.pages.dev/posts/enhancing-observability-with-otel-custom-processors/</link>
      <pubDate>Sun, 27 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/enhancing-observability-with-otel-custom-processors/</guid>
      <description>&lt;p&gt;Observability is crucial for modern distributed systems, enabling engineers to monitor, debug, and optimize their applications effectively. OpenTelemetry (Otel) has emerged as a comprehensive, vendor-neutral observability framework for collecting, processing, and exporting telemetry data such as traces, metrics, and logs.&lt;/p&gt;
&lt;p&gt;This blog post will explore how custom processors in OpenTelemetry can significantly enhance your observability strategy, making it highly customizable and powerful.&lt;/p&gt;
&lt;p&gt;The repo link where I have implemented a very simple Otel-Custom-Processor.&lt;br&gt;
&lt;a href=&#34;https://github.com/AkshayD110/otel-custom-processor/tree/master&#34;&gt;https://github.com/AkshayD110/otel-custom-processor/tree/master&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
