From 618effeb3e3147a4e63dd6eeecbaf146a6ae5ad9 Mon Sep 17 00:00:00 2001 From: Natan Yellin Date: Sun, 10 Dec 2023 21:57:25 +0200 Subject: [PATCH] Update README.md --- README.md | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 1508494e..f625aacd 100644 --- a/README.md +++ b/README.md @@ -283,16 +283,8 @@ krr simple --logtostderr -f yaml > result.yaml
Centralized Prometheus (multi-cluster) +

See below on filtering output from a centralized prometheus, so it matches only one cluster

-If your Prometheus monitors multiple clusters we require the label you defined for your cluster in Prometheus. - -For example, if your cluster has the Prometheus label `cluster: "my-cluster-name"`, then run this command: - -```sh -krr.py simple --prometheus-label cluster -l my-cluster-name -``` - -You may also need the `-p` flag to explicitly give Prometheus' URL.
@@ -447,6 +439,17 @@ If none of those labels result in finding Prometheus, Victoria Metrics or Thanos

(back to top)

+## Scanning with a Centralized Prometheus +If your Prometheus monitors multiple clusters we require the label you defined for your cluster in Prometheus. + +For example, if your cluster has the Prometheus label `cluster: "my-cluster-name"`, then run this command: + +```sh +krr.py simple --prometheus-label cluster -l my-cluster-name +``` + +You may also need the `-p` flag to explicitly give Prometheus' URL. + ## Azure Managed Prometheus For Azure managed Prometheus you need to generate an access token, which can be done by running the following command: