From 7f45aab30760a60d4097bcbc4507b57baf56aa44 Mon Sep 17 00:00:00 2001 From: Angus Jelinek Date: Tue, 27 May 2025 07:54:34 -0700 Subject: [PATCH] Fix env var docs --- .../how_to_guides/toubleshooting_variable_caching.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/observability/how_to_guides/toubleshooting_variable_caching.mdx b/docs/observability/how_to_guides/toubleshooting_variable_caching.mdx index 82549b24c..90f2743a5 100644 --- a/docs/observability/how_to_guides/toubleshooting_variable_caching.mdx +++ b/docs/observability/how_to_guides/toubleshooting_variable_caching.mdx @@ -13,12 +13,12 @@ If you’re not seeing traces in your tracing project or notice traces logged to First, check that the environment variables are set correctly by running: ```python -from langsmith import utils +import os -print(utils.get_env_var("LANGSMITH_PROJECT")) -print(utils.get_env_var("LANGSMITH_TRACING_V2")) -print(utils.get_env_var("LANGSMITH_ENDPOINT")) -print(utils.get_env_var("LANGSMITH_API_KEY")) +print(os.getenv("LANGSMITH_PROJECT")) +print(os.getenv("LANGSMITH_TRACING_V2")) +print(os.getenv("LANGSMITH_ENDPOINT")) +print(os.getenv("LANGSMITH_API_KEY")) ``` If the output does not match what’s defined in your .env file, it’s likely due to environment variable caching.