Fix docs links and build warnings (#636)

* Fix link
* Image alt text

docs/sources/configure/export-modes.md

@@ -24,7 +24,7 @@ Beyla can export data in two modes:
   (using the OpenTelemetry/OTEL protocols) or expose a Prometheus HTTP endpoint ready to be scraped (i.e. **pull** mode).
   In the direct OTEL push mode, the auto-instrumentation tool needs to be configured with the authentication credentials.
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/agent-vs-direct.png)
+![Beyla architecture agent vs direct](https://grafana.com/media/docs/grafana-cloud/beyla/agent-vs-direct.png)
 
 <center><i>Beyla running in Agent mode (left) vs. Direct mode (right)</i></center>
 
@@ -56,9 +56,9 @@ to the different Grafana product endpoints (Mimir and/or Tempo).
 ### Configuring the Agent pipeline
 
 Next, you'll need to specify the following nodes by using the
-[River configuration language](/docs/agent/latest/flow/config-language/):
+[River configuration language](/docs/agent/latest/flow/):
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/nodes.png)
+![Beyla nodes](https://grafana.com/media/docs/grafana-cloud/beyla/nodes.png)
 
 You can download the [example of the whole River configuration file](/docs/beyla/latest/configure/resources/agent-config.river), which will be explained in the rest of this section.
 

docs/sources/quickstart/_index.md

@@ -20,12 +20,6 @@ This section shows how to quickly instrument your applications for different pro
 - [Quickstart: instrument a Rust service with Beyla]({{< relref "./rust.md" >}})
 - [Quickstart: instrument a Java service with Beyla]({{< relref "./java.md" >}})
 
-<!-- TODO: uncomment as long as we create new entries
-* [Quickstart: instrument a .NET service with Beyla]({{< relref "./dotnet.md" >}})
-* [Quickstart: instrument a Nginx server with Beyla]({{< relref "./nginx.md" >}})
-* [Quickstart: instrument an Apache HTTP server with Beyla]({{< relref "./apache.md" >}})
--->
-
 For more information about the different ways you can deploy Beyla (standalone Linux process, Docker container,
 Kubernetes Pod or DaemonSet), refer to the [Set up Beyla]({{< relref "../setup" >}}) section.
 

docs/sources/quickstart/cpp.md

@@ -91,7 +91,7 @@ The above trace shows:
 
 After a few minutes traces will appear in Grafana Cloud. For example, in the traces explorer:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
+![Beyla traces explorer](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
 
 ## 6. Configure routing
 

docs/sources/quickstart/golang.md

@@ -102,7 +102,7 @@ The above trace shows:
 
 After a few minutes traces will appear in Grafana Cloud. For example, in the traces explorer:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace.png)
+![Beyla traces explorer](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace.png)
 
 ## 6. Configure routing
 

docs/sources/quickstart/java.md

@@ -87,7 +87,7 @@ The above trace shows:
 
 After a few minutes traces will appear in Grafana Cloud. For example, in the traces explorer:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
+![Beyla traces explorer](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
 
 ## 6. Configure routing
 

docs/sources/quickstart/nodejs.md

@@ -101,7 +101,7 @@ The above trace shows:
 
 After a few minutes traces will appear in Grafana Cloud. For example, in the traces explorer:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
+![Beyla traces explorer](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
 
 ## 6. Configure routing
 

docs/sources/quickstart/python.md

@@ -99,7 +99,7 @@ The above trace shows:
 
 After a few minutes traces will appear in Grafana Cloud. For example, in the traces explorer:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
+![Beyla traces explorer](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
 
 ## 6. Configure routing
 

docs/sources/quickstart/ruby.md

@@ -99,7 +99,7 @@ The above trace shows:
 
 After a few minutes traces will appear in Grafana Cloud. For example, in the traces explorer:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
+![Beyla traces explorer](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
 
 ## 6. Configure routing
 

docs/sources/quickstart/rust.md

@@ -87,7 +87,7 @@ The above trace shows:
 
 After a few minutes traces will appear in Grafana Cloud. For example, in the traces explorer:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
+![Beyla traces explorer](https://grafana.com/media/docs/grafana-cloud/beyla/quickstart/trace-generic.png)
 
 ## 6. Configure routing
 

docs/sources/requesttime.md

@@ -34,7 +34,7 @@ eBPF allows us to overcome the limitations of manual instrumentation tools. Beyl
 
 Beyla reports traces that are divided in different spans:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/server-side-trace.png)
+![Beyla traces and spans](https://grafana.com/media/docs/grafana-cloud/beyla/server-side-trace.png)
 
 The above image shows the typical structure of a trace as reported by Beyla:
 

docs/sources/tutorial/getting-started.md

@@ -31,7 +31,7 @@ After being the eBPF binaries have been verified they are compiled with a Just-I
 
 The eBPF code is loaded from ordinary applications running in user space. The kernel and the user space applications can share information through a set of well defined communication mechanisms, which are provided by the eBPF specification. For example: ring buffers, arrays, hash maps, etc.
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/ebpf-arch.svg)
+![Beyla eBPF architecture](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/ebpf-arch.svg)
 
 ## Running an instrumented service
 
@@ -188,7 +188,7 @@ There are two ways to forward your OpenTelemetry traces to Grafana Cloud:
 In your Grafana Cloud Portal, click on the "Details" button in the "OpenTelemetry" box. Next,
 copy your Grafana OTLP Endpoint and Instance ID, as in the image below.
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/otlp-connection-details.png)
+![Beyla OTLP connection details](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/otlp-connection-details.png)
 
 Also generate a Password/API token with metrics push privileges.
 
@@ -223,7 +223,7 @@ To verify that metrics are properly received by Grafana, you can go to the left
 choose the Explore tab and your Prometheus data source. Next, write `http_` in the
 Metrics Browser input field and you should see the available metric names in the auto-complete drop-down.
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/dropdown-metrics-v1.0.png)
+![Beyla metrics](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/dropdown-metrics-v1.0.png)
 
 ## Add the Beyla RED Metrics Dashboard
 
@@ -234,7 +234,7 @@ your auto-instrumented RED metrics; to save you time, we provide a sample
 To import the sample dashboard into your Grafana instance, choose "Dashboards" in the Grafana left panel.
 Next, in the Dashboards page, click on the "New" drop-down menu and select "Import":
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/import-dashboard.png)
+![Beyla import dashboard](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/import-dashboard.png)
 
 In the "Import via grafana.com" textbox, copy the Grafana ID from the
 [Beyla RED Metrics](/grafana/dashboards/19923-beyla-red-metrics/)
@@ -245,7 +245,7 @@ data source in the `prometheus-data-source` drop-down at the bottom.
 
 And _voilà!_ you can see some of your test RED metrics:
 
-![](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/beyla-dashboard-screenshot-v1.0.png)
+![Beyla RED metrics](https://grafana.com/media/docs/grafana-cloud/beyla/tutorial/beyla-dashboard-screenshot-v1.0.png)
 
 The dashboard contains the following components: