diff --git a/docs/sources/flow/getting-started/collect-opentelemetry-data.md b/docs/sources/flow/getting-started/collect-opentelemetry-data.md index f67b7327e8b5..ecf484271d37 100644 --- a/docs/sources/flow/getting-started/collect-opentelemetry-data.md +++ b/docs/sources/flow/getting-started/collect-opentelemetry-data.md @@ -20,8 +20,6 @@ This topic describes how to: * Configure batching * Receive OpenTelemetry data over OTLP -[OpenTelemetry]: https://opentelemetry.io - ## Components used in this topic * [otelcol.auth.basic][] @@ -30,12 +28,6 @@ This topic describes how to: * [otelcol.processor.batch][] * [otelcol.receiver.otlp][] -[otelcol.auth.basic]: {{< relref "../reference/components/otelcol.auth.basic.md" >}} -[otelcol.exporter.otlp]: {{< relref "../reference/components/otelcol.exporter.otlp.md" >}} -[otelcol.exporter.otlphttp]: {{< relref "../reference/components/otelcol.exporter.otlphttp.md" >}} -[otelcol.processor.batch]: {{< relref "../reference/components/otelcol.processor.batch.md" >}} -[otelcol.receiver.otlp]: {{< relref "../reference/components/otelcol.receiver.otlp.md" >}} - ## Before you begin * Ensure that you have basic familiarity with instrumenting applications with @@ -45,8 +37,6 @@ This topic describes how to: * Identify where Grafana Agent Flow will write received telemetry data. * Be familiar with the concept of [Components][] in Grafana Agent Flow. -[Components]: {{< relref "../concepts/components.md" >}} - ## Configure an OpenTelemetry Protocol exporter Before components can receive OpenTelemetry data, you must have a component @@ -61,8 +51,6 @@ to forward data to it. > Refer to the list of available [Components][] for the full list of > `otelcol.exporter` components that can be used to export OpenTelemetry data. -> -> [Components]: {{< relref "../reference/components/" >}} To configure an `otelcol.exporter.otlp` component for exporting OpenTelemetry data using OTLP, complete the following steps: @@ -180,8 +168,6 @@ batch data before sending it to our exporter. > `otelcol.processor` components that can be used to process OpenTelemetry > data. You can chain processors by having one processor send data to another > processor. -> -> [Components]: {{< relref "../reference/components/" >}} To configure an `otelcol.processor.batch` component, complete the following steps: @@ -263,8 +249,6 @@ Agent Flow components. > Refer to the list of available [Components][] for the full list of > `otelcol.receiver` components that can be used to receive > OpenTelemetry-compatible data. -> -> [Components]: {{< relref "../reference/components/" >}} To configure an `otelcol.receiver.otlp` component for receiving OTLP data, complete the following steps: @@ -368,3 +352,20 @@ otelcol.exporter.otlp "default" { For more information on receiving OpenTelemetry data using the OpenTelemetry Protocol, refer to [otelcol.receiver.otlp][]. + +[OpenTelemetry]: https://opentelemetry.io + +{{% docs/reference %}} +[otelcol.auth.basic]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.auth.basic.md" +[otelcol.auth.basic]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.auth.basic.md" +[otelcol.exporter.otlp]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.exporter.otlp.md" +[otelcol.exporter.otlp]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.exporter.otlp.md" +[otelcol.exporter.otlphttp]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.exporter.otlphttp.md" +[otelcol.exporter.otlphttp]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.exporter.otlphttp.md" +[otelcol.processor.batch]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.processor.batch.md" +[otelcol.processor.batch]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.processor.batch.md" +[otelcol.receiver.otlp]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.receiver.otlp.md" +[otelcol.receiver.otlp]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.receiver.otlp.md" +[Components]: "/docs/agent/ -> /docs/agent//flow/concepts/components.md" +[Components]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/concepts/components.md" +{{% /docs/reference %}} diff --git a/docs/sources/flow/getting-started/collect-prometheus-metrics.md b/docs/sources/flow/getting-started/collect-prometheus-metrics.md index d4143697e71b..b7bed5f92fe1 100644 --- a/docs/sources/flow/getting-started/collect-prometheus-metrics.md +++ b/docs/sources/flow/getting-started/collect-prometheus-metrics.md @@ -19,18 +19,12 @@ This topic describes how to: * Configure metrics delivery * Collect metrics from Kubernetes Pods -[Prometheus]: https://prometheus.io - ## Components used in this topic * [discovery.kubernetes][] * [prometheus.remote_write][] * [prometheus.scrape][] -[discovery.kubernetes]: {{< relref "../reference/components/discovery.kubernetes.md" >}} -[prometheus.remote_write]: {{< relref "../reference/components/prometheus.remote_write.md" >}} -[prometheus.scrape]: {{< relref "../reference/components/prometheus.scrape.md" >}} - ## Before you begin * Ensure that you have basic familiarity with instrumenting applications with @@ -42,8 +36,6 @@ This topic describes how to: Cloud, or Grafana Enterprise Metrics. * Be familiar with the concept of [Components][] in Grafana Agent Flow. -[Components]: {{< relref "../concepts/components.md" >}} - ## Configure metrics delivery Before components can collect Prometheus metrics, you must have a component @@ -168,7 +160,7 @@ To collect metrics from Kubernetes Pods, complete the following steps: } ``` - 1. If you do not want to search for Pods in the Namespace Grafana + 1. If you don't want to search for Pods in the Namespace Grafana Agent is running in, set `own_namespace` to `false`. 2. Replace `NAMESPACE_NAMES` with a comma-delimited list of strings @@ -233,10 +225,6 @@ To collect metrics from Kubernetes Pods, complete the following steps: 3. Replace `REMOTE_WRITE_LABEL` with the label chosen for your existing `prometheus.remote_write` component. - -[Field Selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/ -[Labels and Selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#set-based-requirement - The following example demonstrates configuring Grafana Agent to collect metrics from running production Kubernetes Pods in the `default` Namespace: @@ -377,10 +365,6 @@ To collect metrics from Kubernetes Services, complete the following steps: 3. Replace `REMOTE_WRITE_LABEL` with the label chosen for your existing `prometheus.remote_write` component. - -[Field Selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/ -[Labels and Selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#set-based-requirement - The following example demonstrates configuring Grafana Agent to collect metrics from running production Kubernetes Services in the `default` Namespace: @@ -497,4 +481,21 @@ prometheus.remote_write "default" { } ``` -[Objects]: {{< relref "../config-language/expressions/types_and_values.md#objects" >}} +[Prometheus]: https://prometheus.io +[Field Selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/ +[Labels and Selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#set-based-requirement +[Field Selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/ +[Labels and Selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#set-based-requirement + +{{% docs/reference %}} +[discovery.kubernetes]: "/docs/agent/ -> /docs/agent//flow/reference/components/discovery.kubernetes.md" +[discovery.kubernetes]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/discovery.kubernetes.md" +[prometheus.remote_write]: "/docs/agent/ -> /docs/agent//flow/reference/components/prometheus.remote_write.md" +[prometheus.remote_write]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/prometheus.remote_write.md" +[prometheus.scrape]: "/docs/agent/ -> /docs/agent//flow/reference/components/prometheus.scrape.md" +[prometheus.scrape]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/prometheus.scrape.md" +[Components]: "/docs/agent/ -> /docs/agent//flow/concepts/components.md" +[Components]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/concepts/components.md" +[Objects]: "/docs/agent/ -> /docs/agent//flow/config-language/expressions/types_and_values.md#objects" +[Objects]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/config-language/expressions/types_and_values.md#objects" +{{% /docs/reference %}} diff --git a/docs/sources/flow/getting-started/configure-agent-clustering.md b/docs/sources/flow/getting-started/configure-agent-clustering.md index b9fdf85c1669..af7085b9d1f1 100644 --- a/docs/sources/flow/getting-started/configure-agent-clustering.md +++ b/docs/sources/flow/getting-started/configure-agent-clustering.md @@ -16,22 +16,21 @@ You can configure Grafana Agent to run with [clustering][] so that individual agents can work together for workload distribution and high availability. -{{% admonition type="note" %}} -Clustering is a [beta]({{< relref "../../stability.md#beta" >}}) feature. Beta features are subject to breaking -changes and may be replaced with equivalent functionality that covers the same -use case. -{{%/admonition %}} -This topic describes how to add clustering to an existing installation. +> **Note:** Clustering is a [beta][] feature. Beta features are subject to breaking changes and may be +> replaced with equivalent functionality that covers the same use case. -[clustering]: {{< relref "../concepts/clustering.md" >}} +This topic describes how to add clustering to an existing installation. ## Configure Grafana Agent clustering with Helm Chart -This section will guide you through enabling clustering when Grafana Agent is +This section guides you through enabling clustering when Grafana Agent is installed on Kubernetes using the [Grafana Agent Helm chart][install-helm]. -[install-helm]: {{< relref "../setup/install/kubernetes.md" >}} +### Before you begin + +- Ensure that your `values.yaml` file has `controller.type` set to + `statefulset`. ### Steps @@ -46,7 +45,7 @@ To configure clustering: enabled: true ``` -1. Upgrade your installation to use the new values.yaml file: +1. Upgrade your installation to use the new `values.yaml` file: ```bash helm upgrade RELEASE_NAME -f values.yaml @@ -55,10 +54,19 @@ To configure clustering: Replace `RELEASE_NAME` with the name of the installation you chose when you installed the Helm chart. -1. Use [UI][] to verify the cluster status: +1. Use the [Grafana Agent UI][UI] to verify the cluster status: 1. Click **Clustering** in the navigation bar. 2. Ensure that all expected nodes appear in the resulting table. -[UI]: {{< relref "../monitoring/debugging.md#clustering-page" >}} +{{% docs/reference %}} +[clustering]: "/docs/agent/ -> /docs/agent//flow/concepts/clustering.md" +[clustering]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/concepts/clustering.md" +[beta]: "/docs/agent/ -> /docs/agent//stability.md#beta" +[beta]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/stability.md#beta" +[install-helm]: "/docs/agent/ -> /docs/agent//flow/setup/install/kubernetes.md" +[install-helm]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/setup/install/kubernetes.md" +[UI]: "/docs/agent/ -> /docs/agent//flow/monitoring/debugging.md#component-detail-page" +[UI]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/monitoring/debugging.md#component-detail-page" +{{% /docs/reference %}} diff --git a/docs/sources/flow/getting-started/distribute-prometheus-scrape-load.md b/docs/sources/flow/getting-started/distribute-prometheus-scrape-load.md index 126fb5107995..b3319b72e193 100644 --- a/docs/sources/flow/getting-started/distribute-prometheus-scrape-load.md +++ b/docs/sources/flow/getting-started/distribute-prometheus-scrape-load.md @@ -17,24 +17,15 @@ Prometheus targets each agent scrapes. [Clustering][] with target auto-distribution allows a fleet of agents to work together to dynamically distribute their scrape load, providing high-availability. -{{% admonition type="note" %}} -Clustering is a [beta]({{< relref "../../stability.md#beta" >}}) feature. Beta features are subject to breaking -changes and may be replaced with equivalent functionality that covers the same -use case. -{{%/admonition %}} - -[Clustering]: {{< relref "../concepts/clustering.md" >}} +> **Note:** Clustering is a [beta][] feature. Beta features are subject to breaking +> changes and may be replaced with equivalent functionality that covers the same use case. ## Before you begin - Familiarize yourself with how to [configure existing Grafana Agent installations][configure-grafana-agent]. - [Configure Prometheus metrics collection][]. - [Configure clustering][] of agents. -- Ensure that all of your clustered agents have the same config file. - -[configure-grafana-agent]: {{< relref "../setup/configure" >}} -[Configure Prometheus metrics collection]: {{< relref "collect-prometheus-metrics.md" >}} -[Configure clustering]: {{< relref "./configure-agent-clustering.md" >}} +- Ensure that all of your clustered agents have the same configuration file. ## Steps @@ -53,10 +44,23 @@ To distribute Prometheus metrics scrape load with clustering: 3. Validate that auto-distribution is functioning: - 1. Using the [UI][] on each agent, navigate to the details page for one of + 1. Using the [Grafana Agent UI][UI] on each agent, navigate to the details page for one of the `prometheus.scrape` components you modified. 2. Compare the Debug Info sections between two different agents to ensure - that they are not scraping the same sets of targets. - -[UI]: {{< relref "../monitoring/debugging.md#component-detail-page" >}} + that they're not scraping the same sets of targets. + +{{% docs/reference %}} +[Clustering]: "/docs/agent/ -> /docs/agent//flow/concepts/clustering.md" +[Clustering]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/concepts/clustering.md" +[beta]: "/docs/agent/ -> /docs/agent//stability.md#beta" +[beta]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/stability.md#beta" +[configure-grafana-agent]: "/docs/agent/ -> /docs/agent//flow/setup/configure" +[configure-grafana-agent]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/setup/configure" +[Configure Prometheus metrics collection]: "/docs/agent/ -> /docs/agent//flow/getting-started/collect-prometheus-metrics.md" +[Configure Prometheus metrics collection]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/getting-started/collect-prometheus-metrics.md" +[Configure clustering]: "/docs/agent/ -> /docs/agent//flow/getting-started/configure-agent-clustering.md" +[Configure clustering]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/getting-started/configure-agent-clustering.md" +[UI]: "/docs/agent/ -> /docs/agent//flow/monitoring/debugging.md#component-detail-page" +[UI]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/monitoring/debugging.md#component-detail-page" +{{% /docs/reference %}} diff --git a/docs/sources/flow/getting-started/migrating-from-prometheus.md b/docs/sources/flow/getting-started/migrating-from-prometheus.md index 4068cee50c49..14e32241f83b 100644 --- a/docs/sources/flow/getting-started/migrating-from-prometheus.md +++ b/docs/sources/flow/getting-started/migrating-from-prometheus.md @@ -19,29 +19,17 @@ This topic describes how to: * Convert a Prometheus configuration to a flow configuration. * Run a Prometheus configuration natively using Grafana Agent flow mode. -[Prometheus]: https://prometheus.io/docs/prometheus/latest/configuration/configuration/ - ## Components used in this topic * [prometheus.scrape][] * [prometheus.remote_write][] -[prometheus.scrape]: {{< relref "../reference/components/prometheus.scrape.md" >}} -[prometheus.remote_write]: {{< relref "../reference/components/prometheus.remote_write.md" >}} - ## Before you begin * You must have an existing Prometheus configuration. * You must have a set of Prometheus applications ready to push telemetry data to Grafana Agent. * You must be familiar with the concept of [Components][] in Grafana Agent flow mode. -[Components]: {{< relref "../concepts/components.md" >}} -[convert]: {{< relref "../reference/cli/convert.md" >}} -[run]: {{< relref "../reference/cli/run.md" >}} -[Start the agent]: {{< relref "../setup/start-agent.md" >}} -[Flow Debugging]: {{< relref "../monitoring/debugging.md" >}} -[debugging]: #debugging - ## Convert a Prometheus configuration To fully migrate your configuration from [Prometheus] to Grafana Agent @@ -79,7 +67,10 @@ additional features available in Grafana Agent flow mode. any non-critical issues and output the flow configuration using a best-effort conversion by including the `--bypass-errors` flag. - {{% admonition type="caution" %}}If you bypass the errors, the behavior of the converted configuration may not match the original Prometheus configuration. Make sure you fully test the converted configuration before using it in a production environment.{{% /admonition %}} + {{% admonition type="caution" %}} + If you bypass the errors, the behavior of the converted configuration may not match the original Prometheus configuration. + Make sure you fully test the converted configuration before using it in a production environment. + {{% /admonition %}} {{< code >}} @@ -139,14 +130,17 @@ This allows you to try flow mode without modifying your existing Prometheus conf 1. Refer to the Grafana Agent [Flow Debugging][] for more information about a running Grafana Agent in flow mode. -1. If your Prometheus configuration cannot be converted and - loaded directly into Grafana Agent, diagnostic information - is sent to `stderr`. You can bypass any non-critical issues +1. If your Prometheus configuration cannot be converted and + loaded directly into Grafana Agent, diagnostic information + is sent to `stderr`. You can bypass any non-critical issues and start the Agent by including the `--config.bypass-conversion-errors` flag in addition to `--config.format=prometheus`. - {{% admonition type="caution" %}}If you bypass the errors, the behavior of the converted configuration may not match the original Prometheus configuration. Do not use this flag in a production environment.{{% /admonition %}} + {{% admonition type="caution" %}} + If you bypass the errors, the behavior of the converted configuration may not match the original Prometheus configuration. + Do not use this flag in a production environment. + {{% /admonition %}} ## Example @@ -173,8 +167,6 @@ remote_write: The convert command takes the YAML file as input and outputs a [River][] file. -[River]: {{< relref "../config-language/_index.md" >}} - {{< code >}} ```static-binary @@ -245,4 +237,26 @@ Furthermore, we recommend that you review the following checklist: produced by Prometheus. * Grafana Agent exposes the [Grafana Agent Flow UI][]. -[Grafana Agent Flow UI]: {{< relref "../monitoring/debugging/#grafana-agent-flow-ui" >}} \ No newline at end of file +[Prometheus]: https://prometheus.io/docs/prometheus/latest/configuration/configuration/ +[debugging]: #debugging + +{{% docs/reference %}} +[prometheus.scrape]: "/docs/agent/ -> /docs/agent//flow/reference/components/prometheus.scrape.md" +[prometheus.scrape]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/prometheus.scrape.md" +[prometheus.remote_write]: "/docs/agent/ -> /docs/agent//flow/reference/components/prometheus.remote_write.md" +[prometheus.remote_write]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/prometheus.remote_write.md" +[Components]: "/docs/agent/ -> /docs/agent//flow/concepts/components.md" +[Components]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/concepts/components.md" +[convert]: "/docs/agent/ -> /docs/agent//flow/reference/cli/convert.md" +[convert]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/cli/convert.md" +[run]: "/docs/agent/ -> /docs/agent//flow/reference/cli/run.md" +[run]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/cli/run.md" +[Start the agent]: "/docs/agent/ -> /docs/agent//flow/setup/start-agent.md" +[Start the agent]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/setup/start-agent.md" +[Flow Debugging]: "/docs/agent/ -> /docs/agent//flow/monitoring/debugging.md" +[Flow Debugging]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/monitoring/debugging.md" +[River]: "/docs/agent/ -> /docs/agent//flow/config-language/_index.md" +[River]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/config-language/_index.md" +[Grafana Agent Flow UI]: "/docs/agent/ -> /docs/agent//flow/monitoring/debugging#grafana-agent-flow-ui" +[Grafana Agent Flow UI]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/monitoring/debugging#grafana-agent-flow-ui" +{{% /docs/reference %}} diff --git a/docs/sources/flow/getting-started/migrating-from-promtail.md b/docs/sources/flow/getting-started/migrating-from-promtail.md index 45a1a4e411bd..7fbe1b109d16 100644 --- a/docs/sources/flow/getting-started/migrating-from-promtail.md +++ b/docs/sources/flow/getting-started/migrating-from-promtail.md @@ -20,30 +20,16 @@ This topic describes how to: * Convert a Promtail configuration to a Flow Mode configuration. * Run a Promtail configuration natively using Grafana Agent Flow Mode. -[Promtail]: /docs/loki/latest/clients/promtail/ - ## Components used in this topic * [local.file_match][] * [loki.source.file][] * [loki.write][] -[local.file_match]: {{< relref "../reference/components/local.file_match.md" >}} -[loki.source.file]: {{< relref "../reference/components/loki.source.file.md" >}} -[loki.write]: {{< relref "../reference/components/loki.write.md" >}} - ## Before you begin * You must have an existing Promtail configuration. -* You must be familiar with the concept of [Components][] in Grafana Agent Flow - Mode. - -[Components]: {{< relref "../concepts/components.md" >}} -[convert]: {{< relref "../reference/cli/convert.md" >}} -[run]: {{< relref "../reference/cli/run.md" >}} -[Start the agent]: {{< relref "../setup/start-agent.md" >}} -[Flow Debugging]: {{< relref "../monitoring/debugging.md" >}} -[debugging]: #debugging +* You must be familiar with the concept of [Components][] in Grafana Agent Flow mode. ## Convert a Promtail configuration @@ -84,7 +70,10 @@ features available in Grafana Agent Flow Mode. output the flow configuration using a best-effort conversion by including the `--bypass-errors` flag. - {{% admonition type="caution" %}}If you bypass the errors, the behavior of the converted configuration may not match the original Promtail configuration. Make sure you fully test the converted configuration before using it in a production environment.{{% /admonition %}} + {{% admonition type="caution" %}} + If you bypass the errors, the behavior of the converted configuration may not match the original Promtail configuration. + Make sure you fully test the converted configuration before using it in a production environment. + {{% /admonition %}} {{< code >}} @@ -132,11 +121,11 @@ configuration. This allows you to try Flow Mode without modifying your existing Promtail configuration infrastructure. > In this task, we will use the [run][] CLI command to run Grafana Agent in Flow -> Mode using a Promtail configuration. +> mode using a Promtail configuration. -[Start the Agent][] in flow mode and include the command line flag +[Start the Agent][] in Flow mode and include the command line flag `--config.format=promtail`. Your configuration file must be a valid Promtail -configuration file rather than a Flow Mode configuration file. +configuration file rather than a Flow mode configuration file. ### Debugging @@ -144,20 +133,23 @@ configuration file rather than a Flow Mode configuration file. a diagnostic report. 1. Refer to the Grafana Agent [Flow Debugging][] for more information about - running Grafana Agent in Flow Mode. + running Grafana Agent in Flow mode. -1. If your Promtail configuration cannot be converted and loaded directly into +1. If your Promtail configuration can't be converted and loaded directly into Grafana Agent, diagnostic information is sent to `stderr`. You can bypass any non-critical issues and start the Agent by including the `--config.bypass-conversion-errors` flag in addition to `--config.format=promtail`. - {{% admonition type="caution" %}}If you bypass the errors, the behavior of the converted configuration may not match the original Promtail configuration. Do not use this flag in a production environment.{{%/admonition %}} + {{% admonition type="caution" %}} + If you bypass the errors, the behavior of the converted configuration may not match the original Promtail configuration. + Do not use this flag in a production environment. + {{%/admonition %}} ## Example This example demonstrates converting a Promtail configuration file to a Grafana -Agent Flow Mode configuration file. +Agent Flow mode configuration file. The following Promtail configuration file provides the input for the conversion: @@ -175,8 +167,6 @@ scrape_configs: The convert command takes the YAML file as input and outputs a [River][] file. -[River]: {{< relref "../config-language/_index.md" >}} - {{< code >}} ```static-binary @@ -214,17 +204,17 @@ loki.write "default" { ## Limitations -Configuration conversion is done on a best-effort basis. The Agent will issue +Configuration conversion is done on a best-effort basis. Grafana Agent will issue warnings or errors where the conversion can't be performed. Once the configuration is converted, we recommend that you review -the Flow Mode configuration file created, and verify that it is correct +the Flow Mode configuration file created, and verify that it's correct before starting to use it in a production environment. Furthermore, we recommend that you review the following checklist: * Check if you are using any extra command line arguments with Promtail which - are not present in your config file. For example, `-max-line-size`. + aren't present in your configuration file. For example, `-max-line-size`. * Check if you are setting any environment variables, whether [expanded in the config file][] itself or consumed directly by Promtail, such as `JAEGER_AGENT_HOST`. @@ -240,6 +230,29 @@ Furthermore, we recommend that you review the following checklist: * Note that the Agent exposes the [Grafana Agent Flow UI][], which differs from Promtail's Web UI. -[expanded in the config file]: /docs/loki/latest/clients/promtail/configuration/#use-environment-variables-in-the-configuration - -[Grafana Agent Flow UI]: {{< relref "../monitoring/debugging/#grafana-agent-flow-ui" >}} +[Promtail]: https://www.grafana.com/docs/loki//clients/promtail/ +[debugging]: #debugging +[expanded in the config file]: https://www.grafana.com/docs/loki//clients/promtail/configuration/#use-environment-variables-in-the-configuration + +{{% docs/reference %}} +[local.file_match]: "/docs/agent/ -> /docs/agent//flow/reference/components/local.file_match.md" +[local.file_match]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/local.file_match.md" +[loki.source.file]: "/docs/agent/ -> /docs/agent//flow/reference/components/loki.source.file.md" +[loki.source.file]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/loki.source.file.md" +[loki.write]: "/docs/agent/ -> /docs/agent//flow/reference/components/loki.write.md" +[loki.write]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/loki.write.md" +[Components]: "/docs/agent/ -> /docs/agent//flow/concepts/components.md" +[Components]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/concepts/components.md" +[convert]: "/docs/agent/ -> /docs/agent//flow/reference/cli/convert.md" +[convert]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/cli/convert.md" +[run]: "/docs/agent/ -> /docs/agent//flow/reference/cli/run.md" +[run]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/cli/run.md" +[Start the agent]: "/docs/agent/ -> /docs/agent//flow/setup/start-agent.md" +[Start the agent]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/setup/start-agent.md" +[Flow Debugging]: "/docs/agent/ -> /docs/agent//flow/monitoring/debugging.md" +[Flow Debugging]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/monitoring/debugging.md" +[River]: "/docs/agent/ -> /docs/agent//flow/config-language/_index.md" +[River]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/config-language/_index.md" +[Grafana Agent Flow UI]: "/docs/agent/ -> /docs/agent//flow/monitoring/debugging#grafana-agent-flow-ui" +[Grafana Agent Flow UI]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/monitoring/debugging#grafana-agent-flow-ui" +{{% /docs/reference %}} diff --git a/docs/sources/flow/getting-started/migrating-from-static.md b/docs/sources/flow/getting-started/migrating-from-static.md index e61f94389182..76b21edba7bc 100644 --- a/docs/sources/flow/getting-started/migrating-from-static.md +++ b/docs/sources/flow/getting-started/migrating-from-static.md @@ -20,8 +20,6 @@ This topic describes how to: * Convert a Grafana Agent Static mode configuration to a Flow mode configuration. * Run a Grafana Agent Static mode configuration natively using Grafana Agent Flow mode. -[Static]: {{< relref "../../static/_index.md" >}} - ## Components used in this topic * [prometheus.scrape][] @@ -31,25 +29,11 @@ This topic describes how to: * [loki.source.file][] * [loki.write][] -[prometheus.scrape]: {{< relref "../reference/components/prometheus.scrape.md" >}} -[prometheus.remote_write]: {{< relref "../reference/components/prometheus.remote_write.md" >}} -[local.file_match]: {{< relref "../reference/components/local.file_match.md" >}} -[loki.process]: {{< relref "../reference/components/loki.process.md" >}} -[loki.source.file]: {{< relref "../reference/components/loki.source.file.md" >}} -[loki.write]: {{< relref "../reference/components/loki.write.md" >}} - ## Before you begin * You must have an existing Grafana Agent Static mode configuration. * You must be familiar with the [Components][] concept in Grafana Agent Flow mode. -[Components]: {{< relref "../concepts/components.md" >}} -[convert]: {{< relref "../reference/cli/convert.md" >}} -[run]: {{< relref "../reference/cli/run.md" >}} -[Start the agent]: {{< relref "../setup/start-agent.md" >}} -[Flow Debugging]: {{< relref "../monitoring/debugging.md" >}} -[debugging]: #debugging - ## Convert a Static mode configuration To fully migrate Grafana Agent from [Static][] mode to Flow mode, you must convert @@ -151,7 +135,7 @@ mode configuration file. 1. Refer to the Grafana Agent [Flow Debugging][] for more information about running Grafana Agent in Flow mode. -1. If your [Static] mode configuration cannot be converted and loaded directly into +1. If your [Static] mode configuration can't be converted and loaded directly into Grafana Agent, diagnostic information is sent to `stderr`. You can use the ` --config.bypass-conversion-errors` flag with `--config.format=static` to bypass any non-critical issues and start the Agent. @@ -220,8 +204,6 @@ logs: The convert command takes the YAML file as input and outputs a [River][] file. -[River]: {{< relref "../config-language/_index.md" >}} - {{< code >}} ```static-binary @@ -309,7 +291,6 @@ loki.write "logs_varlogs" { } external_labels = {} } - ``` ## Limitations @@ -341,12 +322,51 @@ Furthermore, we recommend that you review the following checklist: produced by Static mode. * Grafana Agent exposes the [Grafana Agent Flow UI][]. -[Integrations next]: {{< relref "../../static/configuration/integrations/integrations-next/_index.md" >}} -[Traces]: {{< relref "../../static/configuration/traces-config.md" >}} -[Agent Management]: {{< relref "../../static/configuration/agent-management.md" >}} -[env]: {{< relref "../reference/stdlib/env.md" >}} -[Prometheus Limitations]: {{< relref "migrating-from-prometheus.md/#limitations" >}} -[Promtail Limitations]: {{< relref "migrating-from-promtail.md/#limitations" >}} -[Metrics]: {{< relref "../../static/configuration/metrics-config.md" >}} -[Logs]: {{< relref "../../static/configuration/logs-config.md" >}} -[Grafana Agent Flow UI]: {{< relref "../monitoring/debugging/#grafana-agent-flow-ui" >}} +[debugging]: #debugging + +{{% docs/reference %}} +[Static]: "/docs/agent/ -> /docs/agent//static" +[Static]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/static" +[prometheus.scrape]: "/docs/agent/ -> /docs/agent//flow/reference/components/prometheus.scrape.md" +[prometheus.scrape]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/prometheus.scrape.md" +[prometheus.remote_write]: "/docs/agent/ -> /docs/agent//flow/reference/components/prometheus.remote_write.md" +[prometheus.remote_write]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/prometheus.remote_write.md" +[local.file_match]: "/docs/agent/ -> /docs/agent//flow/reference/components/local.file_match.md" +[local.file_match]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/local.file_match.md" +[loki.process]: "/docs/agent/ -> /docs/agent//flow/reference/components/loki.process.md" +[loki.process]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/loki.process.md" +[loki.source.file]: "/docs/agent/ -> /docs/agent//flow/reference/components/loki.source.file.md" +[loki.source.file]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/loki.source.file.md" +[loki.write]: "/docs/agent/ -> /docs/agent//flow/reference/components/loki.write.md" +[loki.write]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/loki.write.md" +[Components]: "/docs/agent/ -> /docs/agent//flow/concepts/components.md" +[Components]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/concepts/components.md" +[convert]: "/docs/agent/ -> /docs/agent//flow/reference/cli/convert.md" +[convert]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/cli/convert.md" +[run]: "/docs/agent/ -> /docs/agent//flow/reference/cli/run.md" +[run]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/cli/run.md" +[Start the agent]: "/docs/agent/ -> /docs/agent//flow/setup/start-agent.md" +[Start the agent]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/setup/start-agent.md" +[Flow Debugging]: "/docs/agent/ -> /docs/agent//flow/monitoring/debugging.md" +[Flow Debugging]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/monitoring/debugging.md" +[River]: "/docs/agent/ -> /docs/agent//flow/config-language/" +[River]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/config-language/" +[Integrations next]: "/docs/agent/ -> /docs/agent//static/configuration/integrations/integrations-next/_index.md" +[Integrations next]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/static/configuration/traces-config.md +[Traces]: "/docs/agent/ -> /docs/agent//static/configuration/traces-config.md" +[Traces]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/static/configuration/traces-config.md" +[Agent Management]: "/docs/agent/ -> /docs/agent//static/configuration/agent-management.md" +[Agent Management]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/static/configuration/agent-management.md" +[env]: "/docs/agent/ -> /docs/agent//flow/reference/stdlib/env.md" +[env]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/stdlib/env.md" +[Prometheus Limitations]: "/docs/agent/ -> /docs/agent//flow/getting-started/migrating-from-prometheus.md#limitations" +[Prometheus Limitations]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/getting-started/migrating-from-prometheus.md#limitations" +[Promtail Limitations]: "/docs/agent/ -> /docs/agent//flow/getting-started/migrating-from-promtail.md#limitations" +[Promtail Limitations]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/getting-started/migrating-from-promtail.md#limitations" +[Metrics]: "/docs/agent/ -> /docs/agent//static/configuration/metrics-config.md" +[Metrics]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/static/configuration/metrics-config.md" +[Logs]: "/docs/agent/ -> /docs/agent//static/configuration/logs-config.md" +[Logs]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/static/logs-config.md" +[Grafana Agent Flow UI]: "/docs/agent/ -> /docs/agent//flow/monitoring/debugging#grafana-agent-flow-ui" +[Grafana Agent Flow UI]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/monitoring/debugging#grafana-agent-flow-ui" +{{% /docs/reference %}} diff --git a/docs/sources/flow/getting-started/opentelemetry-to-lgtm-stack.md b/docs/sources/flow/getting-started/opentelemetry-to-lgtm-stack.md index 2b680d504c9b..76764fb7276c 100644 --- a/docs/sources/flow/getting-started/opentelemetry-to-lgtm-stack.md +++ b/docs/sources/flow/getting-started/opentelemetry-to-lgtm-stack.md @@ -15,12 +15,9 @@ You can configure Grafana Agent Flow to collect [OpenTelemetry][]-compatible dat This topic describes how to: -* Configure Agent to send your data to Loki -* Configure Agent to send your data to Tempo -* Configure Agent to send your data to Mimir or Prometheus Remote Write - -[OpenTelemetry]: https://opentelemetry.io - +* Configure Grafana Agent to send your data to Loki +* Configure Grafana Agent to send your data to Tempo +* Configure Grafana Agent to send your data to Mimir or Prometheus Remote Write ## Components used in this topic @@ -33,15 +30,6 @@ This topic describes how to: * [otelcol.receiver.otlp][] * [prometheus.remote_write][] -[loki.write]: {{< relref "../reference/components/loki.write.md" >}} -[otelcol.auth.basic]: {{< relref "../reference/components/otelcol.auth.basic.md" >}} -[otelcol.exporter.loki]: {{< relref "../reference/components/otelcol.exporter.loki.md" >}} -[otelcol.exporter.otlp]: {{< relref "../reference/components/otelcol.exporter.otlp.md" >}} -[otelcol.exporter.prometheus]: {{< relref "../reference/components/otelcol.exporter.prometheus.md" >}} -[otelcol.processor.batch]: {{< relref "../reference/components/otelcol.processor.batch.md" >}} -[otelcol.receiver.otlp]: {{< relref "../reference/components/otelcol.receiver.otlp.md" >}} -[prometheus.remote_write]: {{< relref "../reference/components/prometheus.remote_write.md" >}} - ## Before you begin * Ensure that you have basic familiarity with instrumenting applications with @@ -52,11 +40,7 @@ This topic describes how to: * Be familiar with the concept of [Components][] in Grafana Agent Flow. * Complete the [Collect open telemetry data][] getting started guide. You will pick up from where that guide ended. -[Collect open telemetry data]: {{< relref "./collect-opentelemetry-data.md" >}} - -[Components]: {{< relref "../concepts/components.md" >}} - -## The Pipeline +## The pipeline You can start with the Grafana Agent Flow configuration you created in the previous getting started guide: @@ -93,6 +77,7 @@ otelcol.exporter.otlp "default" { ``` The pipeline currently looks like this: + ``` Metrics, Logs, Traces: OTLP Receiver → batch processor → OTLP Exporter ``` @@ -119,7 +104,7 @@ loki.write "default" { } ``` -To use Loki with basic-auth, which is required with GrafanaCloud Loki, you must configure the [loki.write][] component. You can get the Loki config from the Loki **Details** page in the [GrafanaCloud Portal][]: +To use Loki with basic-auth, which is required with Grafana Cloud Loki, you must configure the [loki.write][] component. You can get the Loki configuration from the Loki **Details** page in the [Grafana Cloud Portal][]: ![](../../../assets/getting-started/loki-config.png) @@ -140,11 +125,9 @@ loki.write "grafana_cloud_loki" { } ``` -[Grafana Loki]: /oss/loki/ - ## Grafana Tempo -[Grafana Tempo][] is an open-source, easy-to-use, scalable distributed tracing backend. Tempo can ingest OTLP directly, and you can use the OTLP exporter to send the traces to Tempo. +[Grafana Tempo][] is an open source, easy-to-use, scalable distributed tracing backend. Tempo can ingest OTLP directly, and you can use the OTLP exporter to send the traces to Tempo. ```river otelcol.exporter.otlp "default" { @@ -154,7 +137,7 @@ otelcol.exporter.otlp "default" { } ``` -To use Tempo with basic-auth, which is required with GrafanaCloud Tempo, you must use the [otelcol.auth.basic][] component. You can get the Tempo config from the Tempo **Details** page in the [GrafanaCloud Portal][]: +To use Tempo with basic-auth, which is required with Grafana Cloud Tempo, you must use the [otelcol.auth.basic][] component. You can get the Tempo configuration from the Tempo **Details** page in the [Grafana Cloud Portal][]: ![](../../../assets/getting-started/tempo-config.png) @@ -172,12 +155,9 @@ otelcol.auth.basic "grafana_cloud_tempo" { } ``` -[Grafana Tempo]: https://grafana.com/oss/tempo/ -[GrafanaCloud Portal]: https://grafana.com/docs/grafana-cloud/account-management/cloud-portal/#your-grafana-cloud-stack - ## Grafana Mimir or Prometheus Remote Write -[Prometheus Remote Write][] is a popular metrics transmission protocol supported by most metrics systems, including [Grafana Mimir][] and GrafanaCloud. To send from OTLP to Prometheus, we do a passthrough from the [otelcol.exporter.prometheus][] to the [prometheus.remote_write][] component. The Prometheus remote write component in Agent is a robust protocol implementation, including a Write Ahead Log for resiliency. +[Prometheus Remote Write][] is a popular metrics transmission protocol supported by most metrics systems, including [Grafana Mimir][] and Grafana Cloud. To send from OTLP to Prometheus, we do a passthrough from the [otelcol.exporter.prometheus][] to the [prometheus.remote_write][] component. The Prometheus remote write component in Agent is a robust protocol implementation, including a Write Ahead Log for resiliency. ```river otelcol.exporter.prometheus "default" { @@ -191,7 +171,7 @@ prometheus.remote_write "default" { } ``` -To use Prometheus with basic-auth, which is required with GrafanaCloud Prometheus, you have to configure the [prometheus.remote_write][] component. You can get the Prometheus config from the Prometheus **Details** page in the [GrafanaCloud Portal][]: +To use Prometheus with basic-auth, which is required with Grafana Cloud Prometheus, you must configure the [prometheus.remote_write][] component. You can get the Prometheus configuration from the Prometheus **Details** page in the [Grafana Cloud Portal][]: ![](../../../assets/getting-started/prometheus-config.png) @@ -212,9 +192,6 @@ prometheus.remote_write "grafana_cloud_prometheus" { } ``` -[Prometheus Remote Write]: https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage -[Grafana Mimir]: https://grafana.com/oss/mimir/ - ## Putting it all together Instead of referencing `otelcol.exporter.otlp.default.input` in the output of `otelcol.processor.batch`, we need to reference the three exporters we set up. The final configuration becomes: @@ -321,4 +298,34 @@ ts=2023-05-09T09:37:15.304234Z component=otelcol.receiver.otlp.default level=inf You can now check the pipeline graphically by visiting http://localhost:12345/graph -![](../../../assets/getting-started/otlp-lgtm-graph.png) \ No newline at end of file +![](../../../assets/getting-started/otlp-lgtm-graph.png) + +[OpenTelemetry]: https://opentelemetry.io +[Grafana Loki]: https://grafana.com/oss/loki/ +[Grafana Tempo]: https://grafana.com/oss/tempo/ +[Grafana Cloud Portal]: https://grafana.com/docs/grafana-cloud/account-management/cloud-portal#your-grafana-cloud-stack +[Prometheus Remote Write]: https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage +[Grafana Mimir]: https://grafana.com/oss/mimir/ + +{{% docs/reference %}} +[Collect open telemetry data]: "/docs/agent/ -> /docs/agent//flow/getting-started/collect-opentelemetry-data.md" +[Collect open telemetry data]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/getting-started/collect-opentelemetry-data.md" +[Components]: "/docs/agent/ -> /docs/agent//flow/concepts/components.md" +[Components]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/concepts/components.md" +[loki.write]: "/docs/agent/ -> /docs/agent//flow/reference/components/loki.write.md" +[loki.write]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/loki.write.md" +[otelcol.auth.basic]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.auth.basic.md" +[otelcol.auth.basic]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.auth.basic.md" +[otelcol.exporter.loki]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.exporter.loki.md" +[otelcol.exporter.loki]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.exporter.loki.md" +[otelcol.exporter.otlp]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.exporter.otlp.md" +[otelcol.exporter.otlp]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.exporter.otlp.md" +[otelcol.exporter.prometheus]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.exporter.prometheus.md" +[otelcol.exporter.prometheus]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.exporter.prometheus.md" +[otelcol.processor.batch]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.processor.batch.md" +[otelcol.processor.batch]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.processor.batch.md" +[otelcol.receiver.otlp]: "/docs/agent/ -> /docs/agent//flow/reference/components/otelcol.receiver.otlp.md" +[otelcol.receiver.otlp]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/otelcol.receiver.otlp.md" +[prometheus.remote_write]: "/docs/agent/ -> /docs/agent//flow/reference/components/prometheus.remote_write.md" +[prometheus.remote_write]: "/docs/grafana-cloud/ -> /docs/grafana-cloud/monitor-infrastructure/agent/flow/reference/components/prometheus.remote_write.md" +{{% /docs/reference %}} diff --git a/docs/sources/shared/deploy-agent.md b/docs/sources/shared/deploy-agent.md index 5a6618215d89..ccb4b0e8d6b8 100644 --- a/docs/sources/shared/deploy-agent.md +++ b/docs/sources/shared/deploy-agent.md @@ -6,10 +6,11 @@ aliases: - /docs/grafana-cloud/monitor-infrastructure/integrations/agent/shared/deploy-agent/ canonical: https://grafana.com/docs/agent/latest/shared/deploy-agent/ description: Shared content, deployment topologies for Grafana Agent +title: Deploy Grafana Agent headless: true --- -# Deploying Grafana Agent +# Deploy Grafana Agent Grafana Agent is a flexible, vendor-neutral telemetry collector. This flexibility means that Grafana Agent doesn’t enforce a specific deployment topology