<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configure Grafana Alloy clustering in an existing installation on Grafana Labs</title><link>https://grafana.com/docs/alloy/v1.15/configure/clustering/</link><description>Recent content in Configure Grafana Alloy clustering in an existing installation on Grafana Labs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/docs/alloy/v1.15/configure/clustering/index.xml" rel="self" type="application/rss+xml"/><item><title>Distribute Prometheus metrics scrape load</title><link>https://grafana.com/docs/alloy/v1.15/configure/clustering/distribute-prometheus-scrape-load/</link><pubDate>Mon, 30 Mar 2026 15:47:22 +0000</pubDate><guid>https://grafana.com/docs/alloy/v1.15/configure/clustering/distribute-prometheus-scrape-load/</guid><content><![CDATA[&lt;h1 id=&#34;distribute-prometheus-metrics-scrape-load&#34;&gt;Distribute Prometheus metrics scrape load&lt;/h1&gt;
&lt;p&gt;A good predictor for the size of an Alloy deployment is the number of Prometheus targets each Alloy scrapes.
&lt;a href=&#34;../../clustering/&#34;&gt;Clustering&lt;/a&gt; with target auto-distribution allows a fleet of Alloys to work together to dynamically distribute their scrape load, providing high-availability.&lt;/p&gt;
&lt;h2 id=&#34;before-you-begin&#34;&gt;Before you begin&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Familiarize yourself with how to &lt;a href=&#34;../../../configure/&#34;&gt;configure&lt;/a&gt; Alloy installations.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../collect/prometheus-metrics/&#34;&gt;Configure Prometheus metrics collection&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../clustering/&#34;&gt;Configure clustering&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Ensure that all of your clustered Alloys have the same configuration file.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;steps&#34;&gt;Steps&lt;/h2&gt;
&lt;p&gt;To distribute Prometheus metrics scrape load with clustering:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Add the following block to all &lt;code&gt;prometheus.scrape&lt;/code&gt; components, which should use auto-distribution:&lt;/p&gt;

&lt;div class=&#34;code-snippet &#34;&gt;&lt;div class=&#34;lang-toolbar&#34;&gt;
    &lt;span class=&#34;lang-toolbar__item lang-toolbar__item-active&#34;&gt;Alloy&lt;/span&gt;
    &lt;span class=&#34;code-clipboard&#34;&gt;
      &lt;button x-data=&#34;app_code_snippet()&#34; x-init=&#34;init()&#34; @click=&#34;copy()&#34;&gt;
        &lt;img class=&#34;code-clipboard__icon&#34; src=&#34;/media/images/icons/icon-copy-small-2.svg&#34; alt=&#34;Copy code to clipboard&#34; width=&#34;14&#34; height=&#34;13&#34;&gt;
        &lt;span&gt;Copy&lt;/span&gt;
      &lt;/button&gt;
    &lt;/span&gt;
    &lt;div class=&#34;lang-toolbar__border&#34;&gt;&lt;/div&gt;
  &lt;/div&gt;&lt;div class=&#34;code-snippet &#34;&gt;
    &lt;pre data-expanded=&#34;false&#34;&gt;&lt;code class=&#34;language-alloy&#34;&gt;clustering {
  enabled = true
}&lt;/code&gt;&lt;/pre&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restart or reload Alloys for them to use the new configuration.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Validate that auto-distribution is functioning:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Using the Alloy &lt;a href=&#34;../../../troubleshoot/debug/#component-detail-page&#34;&gt;UI&lt;/a&gt; on each Alloy, navigate to the details page for one of the &lt;code&gt;prometheus.scrape&lt;/code&gt; components you modified.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Compare the Debug Info sections between two different Alloy to ensure that they&amp;rsquo;re not scraping the same sets of targets.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ol&gt;
]]></content><description>&lt;h1 id="distribute-prometheus-metrics-scrape-load">Distribute Prometheus metrics scrape load&lt;/h1>
&lt;p>A good predictor for the size of an Alloy deployment is the number of Prometheus targets each Alloy scrapes.
&lt;a href="../../clustering/">Clustering&lt;/a> with target auto-distribution allows a fleet of Alloys to work together to dynamically distribute their scrape load, providing high-availability.&lt;/p></description></item></channel></rss>