clarify migration usage guide limitation for metamonitoring metric na…

…mes (#5371) Signed-off-by: erikbaranowski <[email protected]> Co-authored-by: Clayton Cornell <[email protected]>
grafana · Oct 5, 2023 · 4d73924 · 4d73924
1 parent 20e7638
commit 4d73924
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/docs/sources/flow/getting-started/migrating-from-prometheus.md b/docs/sources/flow/getting-started/migrating-from-prometheus.md
@@ -206,9 +206,9 @@ Furthermore, we recommend that you review the following checklist:
   additional unsupported features are returned as errors during conversion.
 * Check if you are using any extra command line arguments with Prometheus that
   are not present in your configuration file. For example, `--web.listen-address`.
-* Metrics exposed by the Flow Mode usually match Prometheus metrics but
-  will use a different name. Make sure that you use the new metric names, for example,
-  in your alerts and dashboards queries.
+* Metamonitoring metrics exposed by the Flow Mode usually match Prometheus
+  metamonitoring metrics but will use a different name. Make sure that you use
+  the new metric names, for example, in your alerts and dashboards queries.
 * The logs produced by Grafana Agent will differ from those
   produced by Prometheus.
 * Grafana Agent exposes the [Grafana Agent Flow UI][].

diff --git a/docs/sources/flow/getting-started/migrating-from-promtail.md b/docs/sources/flow/getting-started/migrating-from-promtail.md
@@ -199,9 +199,9 @@ Furthermore, we recommend that you review the following checklist:
   Refer to the [loki.source.file][] documentation for more details. Check if you have any existing
   setup, for example, a Kubernetes Persistent Volume, that you must update to use the new
   positions file path.
-* Metrics exposed by the Flow Mode usually match Promtail metrics but
-  will use a different name. Make sure that you use the new metric names, for example,
-  in your alerts and dashboards queries.
+* Metamonitoring metrics exposed by the Flow Mode usually match Promtail
+  metamonitoring metrics but will use a different name. Make sure that you
+  use the new metric names, for example, in your alerts and dashboards queries.
 * Note that the logs produced by the Agent will differ from those
   produced by Promtail.
 * Note that the Agent exposes the [Grafana Agent Flow UI][], which differs