From f8aea814c57f384f0b320952335ba2a039c2f1cf Mon Sep 17 00:00:00 2001 From: Michel Hollands Date: Thu, 9 May 2024 16:46:43 +0100 Subject: [PATCH] Suggest ratelimiting sample rate for Loki traces Signed-off-by: Michel Hollands --- docs/installation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/installation.md b/docs/installation.md index c49b2b1..2ad89b3 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -187,7 +187,7 @@ For each of the dashboard files in charts/meta-monitoring/src/dashboards folder 1. JAEGER_ENDPOINT: http address of the mmc-alloy service installed by the meta-monitoring chart, for example "http://mmc-alloy:14268/api/traces" 1. JAEGER_AGENT_TAGS: extra tags you would like to add to the spans, for example 'cluster="abc",namespace="def"' - 1. JAEGER_SAMPLER_TYPE: the sampling strategy, for example to sample all use 'const' with a value of 1 for the next environment variable - 1. JAEGER_SAMPLER_PARAM: 1 + 1. JAEGER_SAMPLER_TYPE: the sampling strategy, we suggest setting this to `ratelimiting` so at most 1 trace is accepted per second. See these [docs](https://www.jaegertracing.io/docs/1.57/sampling/) for more options. + 1. JAEGER_SAMPLER_PARAM: 1.0 1. If Loki is installed in a different namespace you can create an [ExternalName service](https://kubernetes.io/docs/concepts/services-networking/service/#externalname) in Kubernetes to point to the mmc-alloy service in the meta monitoring namespace