Update and repalce images

docs/sources/concepts/components.md

@@ -62,7 +62,7 @@ An example pipeline may look like this:
 1. A `discovery.kubernetes` component discovers and exports Kubernetes Pods where metrics can be collected.
 1. A `prometheus.scrape` component references the exports of the previous component, and sends collected metrics to the `prometheus.remote_write` component.
 
-![Flow of example pipeline](/media/docs/agent/concepts_example_pipeline.svg)
+{{< figure src="/media/docs/alloy/diagram-concepts-example-pipeline.png" width="600" alt="Example of a pipeline" >}}
 
 The following configuration file represents the pipeline.
 

docs/sources/concepts/configuration-syntax/expressions/referencing_exports.md

@@ -41,7 +41,7 @@ prometheus.remote_write "onprem" {
 
 In the preceding example, you wired together a very simple pipeline by writing a few {{< param "PRODUCT_NAME" >}} expressions.
 
-![Flow of example pipeline](/media/docs/agent/flow_referencing_exports_diagram.svg)
+{{< figure src="/media/docs/alloy/diagram-referencing-exports.png" alt="Example of a pipeline" >}}
 
 After the value is resolved, it must match the [type][] of the attribute it is assigned to.
 While you can only configure attributes using the basic {{< param "PRODUCT_NAME" >}} types,

docs/sources/reference/components/prometheus.exporter.gcp.md

@@ -14,7 +14,7 @@ Metric names follow the template `stackdriver_<monitored_resource>_<metric_type_
 
 The following example shows a load balancing metric:
 
-![gcp-exporter-config-metric-example](https://grafana.com/media/docs/agent/gcp-exporter-config-metric-example.png)
+{{< figure src="/media/docs/alloy/gcp-exporter-config-metric-example.png" alt="Example GCP exporter configuration metric" >}}
 
 The following list shows its attributes: \
 monitored_resource = `https_lb_rule`\

docs/sources/tasks/opentelemetry-to-lgtm-stack.md

@@ -101,9 +101,7 @@ loki.write "default" {
 ```
 
 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][]:
-
-![](/media/docs/agent/loki-config.png)
+You can get the Loki configuration from the Loki **Details** page in the [Grafana Cloud Portal][].
 
 ```alloy
 otelcol.exporter.loki "grafana_cloud_loki" {
@@ -136,9 +134,7 @@ otelcol.exporter.otlp "default" {
 ```
 
 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][]:
-
-![](/media/docs/agent/tempo-config.png)
+You can get the Tempo configuration from the Tempo **Details** page in the [Grafana Cloud Portal][].
 
 ```alloy
 otelcol.exporter.otlp "grafana_cloud_tempo" {
@@ -173,9 +169,7 @@ prometheus.remote_write "default" {
 ```
 
 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][]:
-
-![](/media/docs/agent/prometheus-config.png)
+You can get the Prometheus configuration from the Prometheus **Details** page in the [Grafana Cloud Portal][].
 
 ```alloy
 otelcol.exporter.prometheus "grafana_cloud_prometheus" {
@@ -301,7 +295,7 @@ ts=2023-05-09T09:37:15.304234Z component=otelcol.receiver.otlp.default level=inf
 
 You can check the pipeline graphically by visiting [http://localhost:12345/graph][]
 
-![](/media/docs/agent/otlp-lgtm-graph.png)
+{{< figure src="/media/docs/alloy/otlp-lgtm-graph.png" alt="Graphical representation of a healthy pipeline" >}}
 
 [OpenTelemetry]: https://opentelemetry.io
 [Grafana Loki]: https://grafana.com/oss/loki/