Update Grafana Alloy landing page (#2470) (#2836)

* Initial updates to landing page * Update front matter * Second pass to clean up content * Update with feedback suggestions * Fix bold formatting * Regenerate files * Switch formatting to use def list * Change to using definition list * Fix some minor formatting * Simplifyy a card description (cherry picked from commit adbd2e9) Co-authored-by: Clayton Cornell <[email protected]>
grafana · Feb 25, 2025 · 6313e11 · 6313e11
1 parent ba55721
commit 6313e11
Show file tree

Hide file tree

Showing 2 changed files with 42 additions and 50 deletions.
diff --git a/docs/sources/_index.md b/docs/sources/_index.md
@@ -17,10 +17,13 @@ hero:
   width: 110
   height: 110
   description: >-
-    Grafana Alloy is a vendor-neutral distribution of the OpenTelemetry (OTel) Collector. Alloy uniquely combines the very best OSS observability signals in the community.
+    Grafana Alloy combines the strengths of the leading collectors into one place. Whether observing applications, infrastructure, or both, Grafana Alloy can collect, process, and export telemetry signals to scale and future-proof your observability approach. 
 cards:
   title_class: pt-0 lh-1
   items:
+    - title: Introduction to Alloy
+      href: ./introduction/
+      description: Learn about what Alloy can do for you.
     - title: Install Alloy
       href: ./set-up/install/
       description: Learn how to install and uninstall Alloy on Docker, Kubernetes, Linux, macOS, or Windows.
@@ -35,10 +38,7 @@ cards:
       description: Learn how to migrate to Alloy from Grafana Agent Operator, Prometheus, Promtail, Grafana Agent Static, or Grafana Agent Flow.
     - title: Collect OpenTelemetry data
       href: ./collect/opentelemetry-data/
-      description: You can configure Alloy to collect OpenTelemetry-compatible data and forward it to any OpenTelemetry-compatible endpoint. Learn how to configure OpenTelemetry data delivery, configure batching, and receive OpenTelemetry data over OTLP.
-    - title: Collect and forward Prometheus metrics
-      href: ./collect/prometheus-metrics/
-      description: You can configure Alloy to collect Prometheus metrics and forward them to any Prometheus-compatible database. Learn how to configure metrics delivery and collect metrics from Kubernetes Pods.
+      description: Learn how to configure OpenTelemetry data delivery, configure batching, and receive OpenTelemetry data over OTLP.
     - title: Concepts
       href: ./get-started/
       description: Learn about components, modules, clustering, and the Alloy configuration syntax.
@@ -53,30 +53,26 @@ cards:
 
 # Overview
 
-{{< param "PRODUCT_NAME" >}} offers native pipelines for [OTel][], [Prometheus][], [Pyroscope][], [Loki][], and many other metrics, logs, traces, and profile tools.
-In addition, you can use {{< param "PRODUCT_NAME" >}} pipelines to do different tasks, such as configure alert rules in Loki and [Mimir][].
-{{< param "PRODUCT_NAME" >}} is fully compatible with the OTel Collector, Prometheus Agent, and [Promtail][].
-You can use {{< param "PRODUCT_NAME" >}} as an alternative to either of these solutions or combine it into a hybrid system of multiple collectors and agents.
-You can deploy {{< param "PRODUCT_NAME" >}} anywhere within your IT infrastructure and pair it with your Grafana stack, a telemetry backend from Grafana Cloud, or any other compatible backend from any other vendor.
-{{< param "PRODUCT_NAME" >}} is flexible, and you can easily configure it to fit your needs in on-prem, cloud-only, or a mix of both.
+{{< figure src="/media/docs/alloy/flow-diagram-small-alloy.png" alt="Alloy flow diagram" >}}
 
-{{< admonition type="tip" >}}
-{{< param "PRODUCT_NAME" >}} uses the same components, code, and concepts that were first introduced in Grafana Agent Flow.
-{{< /admonition >}}
+Collect all your telemetry with one product
 
-## What can {{% param "PRODUCT_NAME" %}} do?
+: Choosing the right tools to collect, process, and export telemetry data can be a confusing and costly experience.
+The broad range of telemetry you need to process and the collectors you choose can vary widely depending on your observability goals.
+In addition, you face the challenge of addressing the constantly evolving needs of your observability strategy.
+For example, you may initially only need application observability, but you then discover that you must add infrastructure observability.
+Many organizations manage and configure multiple collectors to address these challenges, introducing more complexity and potential errors in their obervability strategy.
 
-{{< param "PRODUCT_NAME" >}} is more than just observability signals like metrics, logs, and traces. It provides many features that help you quickly find and process your data in complex environments.
-Some of these features include custom components, GitOps compatibility, clustering support, security, and debugging utilities. Refer to the {{< param "PRODUCT_NAME" >}} [Introduction] for more information on these and other key features.
+All signals, whether application, infrastructure, or both
+
+: {{< param "FULL_PRODUCT_NAME" >}} has native pipelines for leading telemetry signals, such as Prometheus and OpenTelemetry, and databases such as Loki and Pyroscope.
+This permits logs, metrics, traces, and even mature support for profiling.
+
+Enterprise strength observability
+
+: {{< param "FULL_PRODUCT_NAME" >}} improves reliability and provides advanced features for Enterprise needs, such as clusters of fleets and balancing workloads.
+Grafana [Fleet Management](https://grafana.com/docs/grafana-cloud/send-data/fleet-management/) helps you manage multiple {{< param "FULL_PRODUCT_NAME" >}} deployments at scale.
 
 ## Explore
 
 {{< card-grid key="cards" type="simple" >}}
-
-[OTel]: https://opentelemetry.io/ecosystem/distributions/
-[Prometheus]: https://prometheus.io/
-[Pyroscope]: https://grafana.com/docs/pyroscope/
-[Loki]: https://grafana.com/docs/loki/
-[Mimir]: https://grafana.com/docs/mimir/
-[Promtail]: https://grafana.com/docs/loki/latest/send-data/promtail/
-[Introduction]: ./introduction/
diff --git a/docs/sources/_index.md.t b/docs/sources/_index.md.t
@@ -17,10 +17,13 @@ hero:
   width: 110
   height: 110
   description: >-
-    Grafana Alloy is a vendor-neutral distribution of the OpenTelemetry (OTel) Collector. Alloy uniquely combines the very best OSS observability signals in the community.
+    Grafana Alloy combines the strengths of the leading collectors into one place. Whether observing applications, infrastructure, or both, Grafana Alloy can collect, process, and export telemetry signals to scale and future-proof your observability approach. 
 cards:
   title_class: pt-0 lh-1
   items:
+    - title: Introduction to Alloy
+      href: ./introduction/
+      description: Learn about what Alloy can do for you.
     - title: Install Alloy
       href: ./set-up/install/
       description: Learn how to install and uninstall Alloy on Docker, Kubernetes, Linux, macOS, or Windows.
@@ -35,10 +38,7 @@ cards:
       description: Learn how to migrate to Alloy from Grafana Agent Operator, Prometheus, Promtail, Grafana Agent Static, or Grafana Agent Flow.
     - title: Collect OpenTelemetry data
       href: ./collect/opentelemetry-data/
-      description: You can configure Alloy to collect OpenTelemetry-compatible data and forward it to any OpenTelemetry-compatible endpoint. Learn how to configure OpenTelemetry data delivery, configure batching, and receive OpenTelemetry data over OTLP.
-    - title: Collect and forward Prometheus metrics
-      href: ./collect/prometheus-metrics/
-      description: You can configure Alloy to collect Prometheus metrics and forward them to any Prometheus-compatible database. Learn how to configure metrics delivery and collect metrics from Kubernetes Pods.
+      description: Learn how to configure OpenTelemetry data delivery, configure batching, and receive OpenTelemetry data over OTLP.
     - title: Concepts
       href: ./get-started/
       description: Learn about components, modules, clustering, and the Alloy configuration syntax.
@@ -53,30 +53,26 @@ cards:
 
 # Overview
 
-{{< param "PRODUCT_NAME" >}} offers native pipelines for [OTel][], [Prometheus][], [Pyroscope][], [Loki][], and many other metrics, logs, traces, and profile tools.
-In addition, you can use {{< param "PRODUCT_NAME" >}} pipelines to do different tasks, such as configure alert rules in Loki and [Mimir][].
-{{< param "PRODUCT_NAME" >}} is fully compatible with the OTel Collector, Prometheus Agent, and [Promtail][].
-You can use {{< param "PRODUCT_NAME" >}} as an alternative to either of these solutions or combine it into a hybrid system of multiple collectors and agents.
-You can deploy {{< param "PRODUCT_NAME" >}} anywhere within your IT infrastructure and pair it with your Grafana stack, a telemetry backend from Grafana Cloud, or any other compatible backend from any other vendor.
-{{< param "PRODUCT_NAME" >}} is flexible, and you can easily configure it to fit your needs in on-prem, cloud-only, or a mix of both.
+{{< figure src="/media/docs/alloy/flow-diagram-small-alloy.png" alt="Alloy flow diagram" >}}
 
-{{< admonition type="tip" >}}
-{{< param "PRODUCT_NAME" >}} uses the same components, code, and concepts that were first introduced in Grafana Agent Flow.
-{{< /admonition >}}
+Collect all your telemetry with one product
 
-## What can {{% param "PRODUCT_NAME" %}} do?
+: Choosing the right tools to collect, process, and export telemetry data can be a confusing and costly experience.
+The broad range of telemetry you need to process and the collectors you choose can vary widely depending on your observability goals.
+In addition, you face the challenge of addressing the constantly evolving needs of your observability strategy.
+For example, you may initially only need application observability, but you then discover that you must add infrastructure observability.
+Many organizations manage and configure multiple collectors to address these challenges, introducing more complexity and potential errors in their obervability strategy.
 
-{{< param "PRODUCT_NAME" >}} is more than just observability signals like metrics, logs, and traces. It provides many features that help you quickly find and process your data in complex environments.
-Some of these features include custom components, GitOps compatibility, clustering support, security, and debugging utilities. Refer to the {{< param "PRODUCT_NAME" >}} [Introduction] for more information on these and other key features.
+All signals, whether application, infrastructure, or both
+
+: {{< param "FULL_PRODUCT_NAME" >}} has native pipelines for leading telemetry signals, such as Prometheus and OpenTelemetry, and databases such as Loki and Pyroscope.
+This permits logs, metrics, traces, and even mature support for profiling.
+
+Enterprise strength observability
+
+: {{< param "FULL_PRODUCT_NAME" >}} improves reliability and provides advanced features for Enterprise needs, such as clusters of fleets and balancing workloads.
+Grafana [Fleet Management](https://grafana.com/docs/grafana-cloud/send-data/fleet-management/) helps you manage multiple {{< param "FULL_PRODUCT_NAME" >}} deployments at scale.
 
 ## Explore
 
 {{< card-grid key="cards" type="simple" >}}
-
-[OTel]: https://opentelemetry.io/ecosystem/distributions/
-[Prometheus]: https://prometheus.io/
-[Pyroscope]: https://grafana.com/docs/pyroscope/
-[Loki]: https://grafana.com/docs/loki/
-[Mimir]: https://grafana.com/docs/mimir/
-[Promtail]: https://grafana.com/docs/loki/latest/send-data/promtail/
-[Introduction]: ./introduction/