Update metrics for Alloy troubleshooting doc

docs/sources/tempo/troubleshooting/agent.md → docs/sources/tempo/troubleshooting/alloy.md

@@ -5,6 +5,7 @@ description: Gain visibility on how many traces are being pushed to Grafana Allo
 weight: 472
 aliases:
 - ../operations/troubleshooting/agent/
+- ./agent.md # /docs/tempo/<TEMPO_VERSION>/troubleshooting/agent.md
 ---
 
 # Troubleshoot Grafana Alloy
@@ -33,6 +34,22 @@ exporter_sent_spans_ratio_total
 exporter_send_failed_spans_ratio_total
 ```
 
+### Check metrics in Grafana Cloud
+
+If you are using Grafana Alloy to send traces to Grafana Cloud, the metrics are visible at
+`http://localhost:12345/metrics`.
+The `/metrics` HTTP endpoint of the Alloy HTTP server exposes the Alloy component and controller metrics.
+Refer to the [Monitor the Grafana Alloy component controller](https://grafana.com/docs/alloy/latest/troubleshoot/controller_metrics/) documentation for more information.
+
+In your Grafana Cloud instance, they can be checked in the `grafanacloud-usage` data source.
+To view the metrics, use the following steps:
+
+1. From your Grafana instance, select **Explore** in the left menu.
+1. Change the data source to `grafanacloud-usage`.
+1. Type the metric to verify in the text box. If you start with `grafanacloud_traces_`, you can  use autocomplete to browse the list of available metrics.
+
+![Use Explore to check the metrics for traces sent to Grafana Cloud](/media/docs/tempo/screenshot-tempo-trouble-metrics-search.png)
+
 ## Trace span logging
 
 If metrics and logs are looking good, but you are still unable to find traces in Grafana Cloud, you can configure Alloy to output all the traces it receives to the [console](https://grafana.com/docs/tempo/<TEMPO_VERSION>/configuration/grafana-alloy/automatic-logging/).