<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Otlp on Netdata</title><link>https://www.netdata.cloud/tags/otlp/</link><description>Recent content in Otlp on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 13 Aug 2026 08:45:56 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/otlp/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenTelemetry Backend</title><link>https://www.netdata.cloud/opentelemetry/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/opentelemetry/</guid><description>An open OTEL backend with native OTLP ingestion, per-second granularity, ML anomaly detection, and infrastructure correlation. Traces coming soon. No per-metric pricing. No vendor lock-in.</description></item><item><title>OpenTelemetry and Netdata, Today</title><link>https://www.netdata.cloud/blog/opentelemetry-metrics-and-logs-ingestion/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/opentelemetry-metrics-and-logs-ingestion/</guid><description>&lt;p>OpenTelemetry has become the default way to instrument applications and ship telemetry. The hard part has never been the data model. It&amp;rsquo;s been picking a backend that handles OTLP without quietly turning into a per-metric bill or a black box that swallows your data.&lt;/p>
&lt;p>Netdata is a native OTLP backend. Stand up an OpenTelemetry Collector with any of its hundreds of receivers, point its OTLP exporter at Netdata, and you get per-second charts, ML anomaly detection on every signal, AI-assisted troubleshooting, and infrastructure correlation, with no per-metric, per-series, or per-host charges. Metrics and logs work today. Trace support is coming soon.&lt;/p></description></item></channel></rss>