Garrett Guillotte

We may need to replace ref/relrefs to `/docs/grafana-cloud/` with plain Markdown links until we can grok how refs across repos works. CC @chri2547

Just confirmed that we need to rework the links out of grafana/grafana from Hugo refs to Markdown links.

CC @robbymilo - a current real-world example of some of the confusion around Hugo ref/relrefs vs. Markdown links across docs sets.

Noting for posterity: This broke a docs link in the Azure Monitor data source docs, which relied on `metricNamespaces.ts` to list compatibility. See [/docs/sources/datasources/azuremonitor/_index.md](https://github.com/grafana/grafana/blame/7146f2731c4ebc4f93c8fe0c634359c3dd89c6dc/docs/sources/datasources/azuremonitor/_index.md#L108), #51302, #51302, #50788. > Not all...

Notes for docs squad reviewers: - Run `make http-api-docs` from the `grafana` repository root, not from the `docs/` subfolder. While this outputs a file to `docs/sources`, the `make` target is...

@mellieA Can you please clarify @killafunkinmofo's last point re: needing `$values` but not using the Classic condition operation? I'll try to clarify the docs accordingly in the meantime.

> | $labels | The labels from the query or condition. For example, `{{ $labels.instance }}` and `{{ $labels.job }}`. This is unavailable when the rule uses a [classic condition]({{<...

Moving out of draft to request a review. I would prefer to resolve the question about `alertmanagerUid` best practices before merging this, but wouldn't block on it.

The `implementation` key was implemented in #39775 without documentation. #50943 implemented `mimir` as a valid option for `implementation`, also without documentation. This data source appears to be maintained at least...

Filed #57043.