From 94fbb6e31c8b0fc57af14ecd9095560802fde1c5 Mon Sep 17 00:00:00 2001 From: Todd Baert Date: Wed, 27 Sep 2023 10:24:16 -0400 Subject: [PATCH] fixup: more troubleshooting Signed-off-by: Todd Baert --- web-docs/troubleshooting.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/web-docs/troubleshooting.md b/web-docs/troubleshooting.md index 585a9b89c..2fe15df26 100644 --- a/web-docs/troubleshooting.md +++ b/web-docs/troubleshooting.md @@ -1,5 +1,17 @@ # Troubleshooting flagd +## Debugging Evaluations + +If a flag or targeting rule isn't proceeding the way you'd expect, you may want to enable more verbose logging. + +flagd and flagd providers typically have debug or verbose logging modes that you can use for this sort of troubleshooting. +You can do this in the standalone version of flagd by starting it with the `--debug` flag (see [CLI](./reference/flagd-cli/flagd/flagd.md) for more information). + +_In-process_ providers which embed the flag evaluation engine use a logging consistent with their implementation language and SDK. +See your provider's documentation for details on how to enable verbose logging. + +The [detailed evaluation](https://openfeature.dev/docs/reference/concepts/evaluation-api#detailed-evaluation) functions can also be helpful in understanding why an evaluation proceeded a particular way. + ## HTTP Integer Response Behavior Why is my `int` response a `string`?