<?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>Cloud Security on Nubis Morocco</title>
    <link>https://nubis.ma/categories/cloud-security/</link>
    <description>Recent content in Cloud Security on Nubis Morocco</description>
    <generator>Hugo -- 0.148.1</generator>
    <language>en</language>
    <lastBuildDate>Sat, 07 Feb 2026 12:19:21 +0100</lastBuildDate>
    <atom:link href="https://nubis.ma/categories/cloud-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploying an OpenTelemetry-Native LGTM Stack on Kubernetes</title>
      <link>https://nubis.ma/blog/deploying_an_opentelemetry_native_lgtm_stack_on_kubernetes/</link>
      <pubDate>Mon, 27 Oct 2025 07:37:28 +0000</pubDate>
      <guid>https://nubis.ma/blog/deploying_an_opentelemetry_native_lgtm_stack_on_kubernetes/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;https://elbazi.me/observability-2-0-breaking-the-three-pillar-silos-for-good-bf3cdca1f40f&#34;&gt;previous article on Observability 2.0&lt;/a&gt;, I talked about how ClickStack and unified platforms solve the fragmented three-pillar problem by storing everything in ClickHouse. That&amp;rsquo;s the ideal end state — but what if you&amp;rsquo;re not ready to rip and replace your entire stack today?&lt;/p&gt;
&lt;p&gt;This Helm chart is the pragmatic answer. It&amp;rsquo;s still three separate backends under the hood (Loki, Tempo, Mimir), but thanks to OpenTelemetry&amp;rsquo;s OTLP protocol, it &lt;em&gt;feels&lt;/em&gt; like one unified system. Your apps emit OTLP, hit a single gateway, and that gateway routes everything to the right storage. You get centralized ingestion, Grafana pre-wired for correlation, and zero vendor lock-in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
