From 905d14bee78c6596cd287b57f2f4310835a9b7ab Mon Sep 17 00:00:00 2001 From: BlakeFernandez <97479131+BlakeFernandez@users.noreply.github.com> Date: Fri, 26 May 2023 04:29:14 -0500 Subject: [PATCH] Add Prometheus Link for scrape_configs (#9270) **What this PR does / why we need it**: Adds some context to the scrape configs section in Promtail Config Docs to ensure clarity around the connection to Prometheus Here is a link to a slack thread where the customer was confused on this: https://raintank-corp.slack.com/archives/C04KY6NJSCE/p1681761335754199 --------- Co-authored-by: Michel Hollands <42814411+MichelHollands@users.noreply.github.com> Co-authored-by: J Stickler --- docs/sources/clients/promtail/configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/clients/promtail/configuration.md b/docs/sources/clients/promtail/configuration.md index cb64028738..3d0bf77677 100644 --- a/docs/sources/clients/promtail/configuration.md +++ b/docs/sources/clients/promtail/configuration.md @@ -356,7 +356,7 @@ is restarted to allow it to continue from where it left off. ## scrape_configs The `scrape_configs` block configures how Promtail can scrape logs from a series -of targets using a specified discovery method: +of targets using a specified discovery method. Promtail uses the same [Prometheus scrape_configs](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config). This means if you already own a Prometheus instance, the config will be very similar: ```yaml # Name to identify this scrape config in the Promtail UI.