Skip to content

Commit f9b7af8

Browse files
Fix langchain readme typo (open-telemetry#3881)
1 parent b9be76f commit f9b7af8

File tree

1 file changed

+3
-3
lines changed
  • instrumentation-genai/opentelemetry-instrumentation-langchain/examples/manual

1 file changed

+3
-3
lines changed

instrumentation-genai/opentelemetry-instrumentation-langchain/examples/manual/README.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
OpenTelemetry Langcahin Instrumentation Example
1+
OpenTelemetry Langchain Instrumentation Example
22
===============================================
33

44
This is an example of how to instrument Langchain when configuring OpenTelemetry SDK and instrumentations manually.
@@ -8,14 +8,14 @@ Traces include details such as the span name and other attributes.
88

99
Note: `.env <.env>`_ file configures additional environment variables:
1010
- :code:`OTEL_LOGS_EXPORTER=otlp` to specify exporter type.
11-
- :code:`OPENAI_API_KEY` open AI key for accessing the OpenAI API.
11+
- :code:`OPENAI_API_KEY` key for accessing the OpenAI API.
1212
- :code:`OTEL_EXPORTER_OTLP_ENDPOINT` to specify the endpoint for exporting traces (default is http://localhost:4317).
1313

1414
Setup
1515
-----
1616

1717
Minimally, update the `.env <.env>`_ file with your :code:`OPENAI_API_KEY`.
18-
An OTLP compatible endpoint should be listening for traces http://localhost:4317.
18+
An OTLP compatible endpoint should be listening for traces at http://localhost:4317.
1919
If not, update :code:`OTEL_EXPORTER_OTLP_ENDPOINT` as well.
2020

2121
Next, set up a virtual environment like this:

0 commit comments

Comments
 (0)