<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Vector blog on Vector</title><link>https://vector.dev/blog/</link><description>Recent content in The Vector blog on Vector</description><generator>Hugo</generator><language>en-us</language><copyright>Datadog, Inc.</copyright><lastBuildDate>Thu, 13 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://vector.dev/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Celebrating COSE's First Year</title><link>https://vector.dev/blog/cose-first-year/</link><pubDate>Thu, 13 Nov 2025 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/cose-first-year/</guid><description>&lt;h2 x-data="{ show: false }" x-on:mouseover="show = true" x-on:mouseleave="show = false" id="our-journey"&gt;
 Our journey
 &lt;a class="ml-2 relative" x-cloak x-show="show" href="#our-journey"&gt;
 &lt;svg xmlns="http://www.w3.org/2000/svg" class="absolute inset-0 h-full h-6 w-6" fill="none" viewBox="0 0 24 24" stroke="currentColor"&gt;
 &lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M7 20l4-16m2 16l4-16M6 9h14M4 15h14" /&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;In October 2024, the
&lt;a href="https://opensource.datadoghq.com/about/#the-community-open-source-engineering-team" rel="noopener" target="_blank" class="inline-block"&gt;COSE (Community Open Source Engineering)&lt;/a&gt;
team was formed with the mission to strengthen Vector&amp;rsquo;s open source foundation and improve the developer experience.
Today, we&amp;rsquo;re celebrating our first year by highlighting the contributions we&amp;rsquo;ve made to the Vector community. The
COSE team has committed over &lt;strong&gt;550 changes&lt;/strong&gt; to Vector, across &lt;strong&gt;8 major releases&lt;/strong&gt; (0.43.0 through 0.51.0).&lt;/p&gt;</description></item><item><title>Highlights - February 2025</title><link>https://vector.dev/blog/highlights-february-2025/</link><pubDate>Wed, 12 Feb 2025 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/highlights-february-2025/</guid><description>&lt;p&gt;&lt;em&gt;In this blog post we want to highlight some recently added features and guides.&lt;/em&gt;&lt;/p&gt;


&lt;h2 x-data="{ show: false }" x-on:mouseover="show = true" x-on:mouseleave="show = false" id="features"&gt;
 Features
 &lt;a class="ml-2 relative" x-cloak x-show="show" href="#features"&gt;
 &lt;svg xmlns="http://www.w3.org/2000/svg" class="absolute inset-0 h-full h-6 w-6" fill="none" viewBox="0 0 24 24" stroke="currentColor"&gt;
 &lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M7 20l4-16m2 16l4-16M6 9h14M4 15h14" /&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;A new OpenTelemetry sink is now available. You can find a
&lt;a href="https://vector.dev/docs/reference/configuration/sinks/opentelemetry/#quickstart"&gt;quickstart guide here&lt;/a&gt;.
&lt;ul&gt;
&lt;li&gt;We have more plans here such as gRPC support and smart grouping at the sink.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;We introduced a new exclusive route transform. You can read more in our
&lt;a href="https://vector.dev/highlights/2024-11-07-exclusive_route/"&gt;release highlight&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Apple Silicon builds are now available in our &lt;a href="https://vector.dev/download/"&gt;downloads page&lt;/a&gt;.
Note that these are available since &lt;code&gt;v0.44.0&lt;/code&gt; and won&amp;rsquo;t show up for older versions.&lt;/li&gt;
&lt;li&gt;A new type of &lt;code&gt;enrichment_table&lt;/code&gt;, called &lt;code&gt;memory&lt;/code&gt;, was introduced! This table can also function as a sink and addresses several new use cases. See this
&lt;a href="https://vector.dev/highlights/2025-02-24-memory_enrichment_table/"&gt;release highlight&lt;/a&gt; for details.&lt;/li&gt;
&lt;li&gt;The VRL function library keeps growing thanks to community contributions! You can read more:
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://vector.dev/releases/0.44.0/#new-features"&gt;0.21.0 Features&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://vector.dev/releases/0.43.0/#new-features"&gt;0.20.0 Features&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;


&lt;h3 x-data="{ show: false }" x-on:mouseover="show = true" x-on:mouseleave="show = false" id="guides"&gt;
 Guides
 &lt;a class="ml-2 relative" x-cloak x-show="show" href="#guides"&gt;
 &lt;svg xmlns="http://www.w3.org/2000/svg" class="absolute inset-0 h-full h-5 w-5" fill="none" viewBox="0 0 24 24" stroke="currentColor"&gt;
 &lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M7 20l4-16m2 16l4-16M6 9h14M4 15h14" /&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h3&gt;&lt;p&gt;We recently added a new guide category: &lt;a href="https://vector.dev/guides/developer/"&gt;Development&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Log Namespacing</title><link>https://vector.dev/blog/log-namespacing/</link><pubDate>Fri, 30 Jun 2023 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/log-namespacing/</guid><description>&lt;div class="admonition no-prose rounded-xl border-3 px-3 py-3.5 lg:px-5 lg:py-4 border-blue-400"&gt;
 &lt;div class="flex items-center"&gt;
 &lt;div class="flex-shrink-0"&gt;
 &lt;svg class="h-6 w-6 text-blue-400" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20" fill="currentColor" aria-hidden="true"&gt;
 
 
 &lt;path fill-rule="evenodd" d="M18 10a8 8 0 11-16 0 8 8 0 0116 0zm-7-4a1 1 0 11-2 0 1 1 0 012 0zM9 9a1 1 0 000 2v3a1 1 0 001 1h1a1 1 0 100-2v-3a1 1 0 00-1-1H9z" clip-rule="evenodd" /&gt;
 

 

 

 

 

 
 &lt;/svg&gt;
 &lt;/div&gt;
 &lt;div class="ml-6 flex flex-col m-0 space-y-1.5"&gt;
 

 &lt;div class="tracking-tight leading-snug dark:prose-dark prose max-w-none"&gt;
 Please visit our &lt;a href="https://vector.dev/guides/level-up/log_namespace/"&gt;log namespace guide&lt;/a&gt; for more details.
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
&lt;/div&gt;

&lt;p&gt;The Vector team has been hard at work improving the data model of events in Vector. These
changes are now available for beta testing for those who want to try it out and give feedback.
This is an opt-in feature. Nothing should change unless you specifically enable it.&lt;/p&gt;</description></item><item><title>Monitoring Vector's per-component memory usage</title><link>https://vector.dev/blog/tracking-allocations/</link><pubDate>Wed, 14 Dec 2022 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/tracking-allocations/</guid><description>&lt;p&gt;We are excited to announce that Vector now has support for exposing per-component memory usage metrics. This work addresses an often-requested feature from users who want to understand how Vector uses memory, and what parts of their configurations are responsible for high memory usage.&lt;/p&gt;


&lt;h2 x-data="{ show: false }" x-on:mouseover="show = true" x-on:mouseleave="show = false" id="trying-it-out"&gt;
 Trying it out
 &lt;a class="ml-2 relative" x-cloak x-show="show" href="#trying-it-out"&gt;
 &lt;svg xmlns="http://www.w3.org/2000/svg" class="absolute inset-0 h-full h-6 w-6" fill="none" viewBox="0 0 24 24" stroke="currentColor"&gt;
 &lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M7 20l4-16m2 16l4-16M6 9h14M4 15h14" /&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;&lt;img src="https://vector.dev/img/blog/vector-top-allocation-tracking.png" alt="vector top with allocation tracing"&gt;&lt;/p&gt;</description></item><item><title>Vector Remap Language</title><link>https://vector.dev/blog/vector-remap-language/</link><pubDate>Mon, 15 Feb 2021 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/vector-remap-language/</guid><description>&lt;p&gt;&lt;strong&gt;Vector Remap Language&lt;/strong&gt; (VRL) is an &lt;a href="https://en.wikipedia.org/wiki/Expression-oriented_programming_language" rel="noopener" target="_blank" class="inline-block"&gt;expression-oriented&lt;/a&gt;
language designed to work with observability data (logs and metrics) in a &lt;em&gt;safe&lt;/em&gt;
and &lt;em&gt;performant&lt;/em&gt; manner. It features a &lt;a href="https://vector.dev/docs/reference/vrl/expressions/"&gt;simple syntax&lt;/a&gt;, a rich
set of &lt;a href="https://vector.dev/docs/reference/vrl/functions/"&gt;built-in functions&lt;/a&gt; tailored to observability use cases,
and &lt;a href="#features"&gt;numerous features&lt;/a&gt; that set it far apart from other options.
This &lt;a href="https://vector.dev/releases/0.12.0/"&gt;0.12&lt;/a&gt; release of Vector marks the official release of the language.&lt;/p&gt;</description></item><item><title>Accelerating Vector with Datadog</title><link>https://vector.dev/blog/datadog-acquisition/</link><pubDate>Thu, 11 Feb 2021 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/datadog-acquisition/</guid><description>&lt;p&gt;We&amp;rsquo;re excited to announce that Timber and Vector are now officially part of &lt;a href="https://www.datadoghq.com" rel="noopener" target="_blank" class="inline-block"&gt;Datadog&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;When we started building Vector, we set out to provide an entirely new kind of data pipeline. We were guided by a belief that when it comes to collecting, transforming, and routing observability data, teams shouldn’t have to accept trade-offs between cost, performance, reliability, and security. They also shouldn’t have to stitch together disparate tools just to get their data from point A to B; the ideal solution should be simple, yet robust, and unify the entire pipeline. We’ve dedicated ourselves to that challenge, and we’re proud of the platform we’ve created.&lt;/p&gt;</description></item><item><title>The new GraphQL API for Vector</title><link>https://vector.dev/blog/graphql-api/</link><pubDate>Tue, 08 Dec 2020 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/graphql-api/</guid><description>&lt;p&gt;Although Vector is an observability tool, it&amp;rsquo;s nonetheless important to be able
to observe Vector itself, especially in production environments where it serves
as critical infrastructure. That&amp;rsquo;s why we&amp;rsquo;re excited to announce the new &lt;a href="https://vector.dev/docs/reference/api/" rel="noopener" target="_blank" class="inline-block"&gt;Vector
GraphQL API&lt;/a&gt;, available in
&lt;a href="https://vector.dev/releases/0.11.0/" rel="noopener" target="_blank" class="inline-block"&gt;v0.11.0&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The API enables ad-hoc querying of:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Your Vector topology, including
&lt;a href="https://vector.dev/docs/reference/configuration/sources/" rel="noopener" target="_blank" class="inline-block"&gt;&lt;code&gt;sources&lt;/code&gt;&lt;/a&gt;,
&lt;a href="https://vector.dev/docs/reference/configuration/transforms/" rel="noopener" target="_blank" class="inline-block"&gt;&lt;code&gt;transforms&lt;/code&gt;&lt;/a&gt; and
&lt;a href="https://vector.dev/docs/reference/configuration/sinks/" rel="noopener" target="_blank" class="inline-block"&gt;&lt;code&gt;sinks&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Uptime and health information.&lt;/li&gt;
&lt;li&gt;Event processing, byte processing, and error metrics, both per component and
in aggregate across the Vector instance.&lt;/li&gt;
&lt;li&gt;Changes to your pipeline configuration, in real time.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This is just the beginning. In the near future, the API will enable you to both
observe &lt;em&gt;and&lt;/em&gt; control Vector remotely, programmatically, and on demand. Stay
tuned!&lt;/p&gt;</description></item><item><title>First-class Kubernetes integration for Vector</title><link>https://vector.dev/blog/kubernetes-integration/</link><pubDate>Thu, 26 Nov 2020 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/kubernetes-integration/</guid><description>&lt;p&gt;After months of development, &lt;a href="https://github.com/vectordotdev/vector/pulls?q=is%3Apr&amp;#43;sort%3Aupdated-desc&amp;#43;kubernetes&amp;#43;is%3Aclosed" rel="noopener" target="_blank" class="inline-block"&gt;over 100 pull requests&lt;/a&gt;, and intensive QA in clusters producing over 20 terabytes of event data a day, we&amp;rsquo;re pleased to announce our first-class &lt;a href="https://kubernetes.io" rel="noopener" target="_blank" class="inline-block"&gt;Kubernetes&lt;/a&gt; integration for Vector in &lt;a href="https://vector.dev/releases/0.11.0/"&gt;version 0.11&lt;/a&gt;. We strove to make even this initial integration rock solid and production ready because we aim to make Vector the default pipeline for all Kubernetes observability data.&lt;/p&gt;
&lt;p&gt;To cut straight to the chase, checkout the &lt;a href="https://vector.dev/docs/setup/installation/platforms/kubernetes/#install"&gt;installation instructions&lt;/a&gt;, otherwise read on for the details.&lt;/p&gt;</description></item><item><title>Adaptive request concurrency. Resilient observability at scale.</title><link>https://vector.dev/blog/adaptive-request-concurrency/</link><pubDate>Tue, 24 Nov 2020 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/adaptive-request-concurrency/</guid><description>&lt;p&gt;Observability pipelines have become critical infrastructure in the current technological landscape, which is why we&amp;rsquo;ve built &lt;a href="https://vector.dev/"&gt;Vector&lt;/a&gt; to provide extremely high throughput with the tiniest resource footprint we can manage (&lt;a href="https://rust-lang.org" rel="noopener" target="_blank" class="inline-block"&gt;Rust&lt;/a&gt; is a huge help here). But this is not enough in the real world: your observability pipeline needs to provide optimal performance and efficiency while &lt;em&gt;also&lt;/em&gt; being a good infrastructure citizen and playing nicely with services like &lt;a href="https://vector.dev/docs/reference/configuration/sinks/elasticsearch/"&gt;Elasticsearch&lt;/a&gt; and &lt;a href="https://vector.dev/docs/reference/configuration/sinks/clickhouse/"&gt;Clickhouse&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;And so we&amp;rsquo;re excited to announce that Vector version 0.11 includes support for &lt;strong&gt;Adaptive Request Concurrency&lt;/strong&gt; (ARC) in all of its HTTP-based &lt;a href="https://vector.dev/docs/reference/configuration/sinks/"&gt;sinks&lt;/a&gt;. This feature does away with static rate limits and automatically optimizes HTTP concurrency limits based on downstream service responses. The underlying &lt;a href="#how-it-works"&gt;mechanism&lt;/a&gt; is a feedback loop inspired by TCP congestion control algorithms.&lt;/p&gt;</description></item><item><title>How we test Vector</title><link>https://vector.dev/blog/how-we-test-vector/</link><pubDate>Mon, 13 Jul 2020 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/how-we-test-vector/</guid><description>&lt;p&gt;When we set out to build Vector, we knew that reliability and performance were
two of our top priorities. We also knew that even the best of intentions would
not be enough to make certain those qualities were realized and reflected in our
users&amp;rsquo; production deployments. Since then, we&amp;rsquo;ve been continuously evolving and
expanding our approach to achieving that level of quality.&lt;/p&gt;</description></item><item><title>Introducing Vector</title><link>https://vector.dev/blog/introducing-vector/</link><pubDate>Mon, 13 Jul 2020 00:00:00 +0000</pubDate><guid>https://vector.dev/blog/introducing-vector/</guid><description>&lt;p&gt;Today we&amp;rsquo;re very excited to open source the Vector project! Vector is a tool for building flexible and robust pipelines for your logs and metrics data. We&amp;rsquo;re still in the early stages, but our goal with Vector is to dramatically simplify your observability infrastructure while making it easy to get more value from your data.&lt;/p&gt;</description></item></channel></rss>