<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Connect tools under one big tent on Grafana Labs</title><link>https://grafana.com/docs/learning-hub/is-grafana-cloud-right-for-me/01-data-everywhere/</link><description>Recent content in Connect tools under one big tent on Grafana Labs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/docs/learning-hub/is-grafana-cloud-right-for-me/01-data-everywhere/index.xml" rel="self" type="application/rss+xml"/><item><title>Meet your data where it is</title><link>https://grafana.com/docs/learning-hub/is-grafana-cloud-right-for-me/01-data-everywhere/01-module-intro/</link><pubDate>Wed, 17 Jun 2026 14:30:30 -0500</pubDate><guid>https://grafana.com/docs/learning-hub/is-grafana-cloud-right-for-me/01-data-everywhere/01-module-intro/</guid><content><![CDATA[&lt;h2 id=&#34;data-and-tools-everywhere&#34;&gt;Data and tools everywhere&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Metrics, logs, traces, and profiles live in different vendors, regions, and stacks&lt;/li&gt;
&lt;li&gt;Investigations require switching tools mid-incident&lt;/li&gt;
&lt;li&gt;Each new source adds another query language and tool to learn&lt;/li&gt;
&lt;li&gt;Some data can&amp;rsquo;t leave your network because of security, compliance, or data-residency rules&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;solutions&#34;&gt;Solutions&lt;/h2&gt;
&lt;p&gt;You can send data to Grafana Cloud or connect to it where it lives. Many teams use both.
&lt;img
  class=&#34;lazyload d-inline-block&#34;
  data-src=&#34;push-vs-pull.svg&#34;
  alt=&#34;Two ways to get data into Grafana Cloud: send or connect&#34;/&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Send data to Cloud.&lt;/strong&gt; Send your telemetry to managed backends. Grafana can perform storage and scaling for you. Your options include:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;/docs/grafana-cloud/send-data/alloy/&#34;&gt;Grafana Alloy&lt;/a&gt;, a vendor-neutral OpenTelemetry Collector distribution&lt;/li&gt;
&lt;li&gt;The OpenTelemetry-native &lt;a href=&#34;/docs/grafana-cloud/send-data/otlp/&#34;&gt;OTLP endpoint&lt;/a&gt; for OTel SDKs and collectors&lt;/li&gt;
&lt;li&gt;Existing agents and formats, including &lt;a href=&#34;/docs/grafana-cloud/send-data/metrics/&#34;&gt;Prometheus, Graphite, InfluxDB, and Datadog&lt;/a&gt; for metrics and &lt;a href=&#34;/docs/grafana-cloud/send-data/traces/&#34;&gt;Jaeger and Zipkin&lt;/a&gt; for traces&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/docs/grafana-cloud/monitor-infrastructure/integrations/&#34;&gt;Integrations&lt;/a&gt; that set up collection plus preconfigured dashboards and alerts for common technologies, including operating systems, databases, web servers, and cloud services, in minutes&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Connect to data where it lives.&lt;/strong&gt; Keep your data in its existing location.
&lt;ul&gt;
&lt;li&gt;Query existing systems through &lt;a href=&#34;/docs/grafana-cloud/connect-externally-hosted/&#34;&gt;data source plugins&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reach sources that can&amp;rsquo;t leave your network with &lt;a href=&#34;/docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/&#34;&gt;Private Data Source Connect&lt;/a&gt;, which keeps them off the public internet&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;real-results-from-real-teams&#34;&gt;Real results from real teams&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;/success/syso/&#34;&gt;&lt;strong&gt;SYSO&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;We use Grafana to get that consistent view across all the different types of assets that we manage, so the operations team can make sure we are maximizing the revenue of those assets for our customers.&amp;rdquo;&lt;/p&gt;&lt;/blockquote&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;/success/miq/&#34;&gt;&lt;strong&gt;MiQ&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;What used to take 45 minutes to an hour now takes about 10 to 15 minutes.&amp;rdquo;&lt;/p&gt;&lt;/blockquote&gt;
&lt;/li&gt;
&lt;/ul&gt;
]]></content><description>&lt;h2 id="data-and-tools-everywhere">Data and tools everywhere&lt;/h2>
&lt;ul>
&lt;li>Metrics, logs, traces, and profiles live in different vendors, regions, and stacks&lt;/li>
&lt;li>Investigations require switching tools mid-incident&lt;/li>
&lt;li>Each new source adds another query language and tool to learn&lt;/li>
&lt;li>Some data can&amp;rsquo;t leave your network because of security, compliance, or data-residency rules&lt;/li>
&lt;/ul>
&lt;h2 id="solutions">Solutions&lt;/h2>
&lt;p>You can send data to Grafana Cloud or connect to it where it lives. Many teams use both.
&lt;img
class="lazyload d-inline-block"
data-src="push-vs-pull.svg"
alt="Two ways to get data into Grafana Cloud: send or connect"/>&lt;/p></description></item><item><title>Manage collectors at scale</title><link>https://grafana.com/docs/learning-hub/is-grafana-cloud-right-for-me/01-data-everywhere/02-fleet-management/</link><pubDate>Wed, 17 Jun 2026 12:54:46 -0500</pubDate><guid>https://grafana.com/docs/learning-hub/is-grafana-cloud-right-for-me/01-data-everywhere/02-fleet-management/</guid><content><![CDATA[&lt;h2 id=&#34;one-collector-is-easy-a-fleet-isnt&#34;&gt;One collector is easy. A fleet isn&amp;rsquo;t.&lt;/h2&gt;
&lt;p&gt;Sending telemetry from a single collector is simple. Doing it across hundreds of collectors, in different environments and on different machines, is where the work piles up. Each one has a configuration to maintain, and keeping them consistent by hand doesn&amp;rsquo;t scale.&lt;/p&gt;
&lt;h2 id=&#34;manage-the-whole-fleet-from-one-place&#34;&gt;Manage the whole fleet from one place&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;/docs/grafana-cloud/send-data/fleet-management/&#34;&gt;Fleet Management&lt;/a&gt; is a Grafana Cloud feature for managing many collector deployments of &lt;a href=&#34;/docs/grafana-cloud/send-data/alloy/&#34;&gt;Grafana Alloy&lt;/a&gt; at once. From the Grafana Cloud interface, you can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;See fleet health at a glance.&lt;/strong&gt; An overview dashboard shows collector counts, versions, operating systems, and health across the whole fleet.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Monitor individual collectors.&lt;/strong&gt; Inspect any collector&amp;rsquo;s health, logs, attributes, and configuration errors from its details view.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Configure collectors remotely.&lt;/strong&gt; Create configuration pipelines once and assign them to collectors by attribute, with no per-machine scripting.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Control cost and collection.&lt;/strong&gt; Turn data streams on and off to keep telemetry focused and reduce overload.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;real-results-from-real-teams&#34;&gt;Real results from real teams&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;/blog/telemetry-pipeline-management-at-any-scale-fleet-management-in-grafana-cloud-is-generally-available/&#34;&gt;&lt;strong&gt;Tarbell Management Group&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Managing everything within Fleet Management makes configuring collectors effortless. The correct configuration is applied automatically across our infrastructure, whether it&amp;rsquo;s a point-of-sale system, a user PC, or a Kubernetes service.&amp;rdquo;&lt;/p&gt;&lt;/blockquote&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;/events/observabilitycon/agenda/2025/axa-observability-at-scale-with-opentelemetry/&#34;&gt;&lt;strong&gt;AXA Germany&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Moving to Grafana Cloud reduced our complexity… nobody wants to maintain a huge amount of infrastructure. Everybody wants to do the new cool stuff.&amp;rdquo;&lt;/p&gt;&lt;/blockquote&gt;
&lt;/li&gt;
&lt;/ul&gt;
]]></content><description>&lt;h2 id="one-collector-is-easy-a-fleet-isnt">One collector is easy. A fleet isn&amp;rsquo;t.&lt;/h2>
&lt;p>Sending telemetry from a single collector is simple. Doing it across hundreds of collectors, in different environments and on different machines, is where the work piles up. Each one has a configuration to maintain, and keeping them consistent by hand doesn&amp;rsquo;t scale.&lt;/p></description></item><item><title>Vendor lock-in</title><link>https://grafana.com/docs/learning-hub/is-grafana-cloud-right-for-me/01-data-everywhere/03-open-standards/</link><pubDate>Wed, 17 Jun 2026 12:54:46 -0500</pubDate><guid>https://grafana.com/docs/learning-hub/is-grafana-cloud-right-for-me/01-data-everywhere/03-open-standards/</guid><content><![CDATA[&lt;h2 id=&#34;vendor-lock-in&#34;&gt;Vendor lock-in&lt;/h2&gt;
&lt;p&gt;With many observability vendors, moving away means starting from scratch:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Dashboards stored in proprietary formats&lt;/li&gt;
&lt;li&gt;Queries written in vendor-specific languages&lt;/li&gt;
&lt;li&gt;Data locked behind APIs you don&amp;rsquo;t control&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;the-difference-with-grafana-cloud&#34;&gt;The difference with Grafana Cloud&lt;/h2&gt;
&lt;p&gt;Built on open-source and open-standard foundations, any switching is a migration, not a rewrite. Your dashboards, alert rules, and instrumentation move with you, because they&amp;rsquo;re built on open formats, not locked to our platform.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard formats&lt;/strong&gt;: Cloud uses the same dashboards and alert rules as open source Grafana.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Query languages&lt;/strong&gt;: Cloud uses the open query languages of Prometheus, Loki, and Tempo: PromQL, LogQL, and TraceQL.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Standard APIs&lt;/strong&gt;: Cloud exposes open APIs (Prometheus remote write, OTLP, and others) so your tooling isn&amp;rsquo;t tied to a proprietary integration layer.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;real-results-from-real-teams&#34;&gt;Real results from real teams&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;/success/erste-digital/&#34;&gt;&lt;strong&gt;Erste Digital&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;We wanted to have a vendor neutral instrumentation and therefore we chose Grafana Cloud.&amp;rdquo;&lt;/p&gt;&lt;/blockquote&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&#34;/success/auditboard/&#34;&gt;&lt;strong&gt;Optro&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Grafana Cloud&amp;rsquo;s native support for OpenTelemetry would allow the team to future-proof their stack. Open standards offered greater flexibility around data collection and integration.&lt;/p&gt;&lt;/blockquote&gt;
&lt;/li&gt;
&lt;/ul&gt;
]]></content><description>&lt;h2 id="vendor-lock-in">Vendor lock-in&lt;/h2>
&lt;p>With many observability vendors, moving away means starting from scratch:&lt;/p>
&lt;ul>
&lt;li>Dashboards stored in proprietary formats&lt;/li>
&lt;li>Queries written in vendor-specific languages&lt;/li>
&lt;li>Data locked behind APIs you don&amp;rsquo;t control&lt;/li>
&lt;/ul>
&lt;h2 id="the-difference-with-grafana-cloud">The difference with Grafana Cloud&lt;/h2>
&lt;p>Built on open-source and open-standard foundations, any switching is a migration, not a rewrite. Your dashboards, alert rules, and instrumentation move with you, because they&amp;rsquo;re built on open formats, not locked to our platform.&lt;/p></description></item></channel></rss>