HYBIM-696: Fix openai-v2 PyPI page links and README (#333)

- Update PyPI badge to splunk-otel-instrumentation-openai
- Fix pip install command to use correct Splunk package name
- Update References link to SDOT GitHub repo
- Fix project URLs in pyproject.toml to signalfx/splunk-otel-python-contrib

Author: shuwpan

instrumentation-genai/opentelemetry-instrumentation-openai-v2/CHANGELOG.md

@@ -15,6 +15,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Add `gen_ai.request.stream` attribute for streaming requests
 - Add `gen_ai.response.time_to_first_chunk` attribute and metric for streaming requests
 
+### Fixed
+
+- Fix PyPI badge, install command, and references in README.rst to use correct
+  `splunk-otel-instrumentation-openai` package name instead of upstream
+- Fix project URLs in pyproject.toml to point to SDOT repo (`signalfx/splunk-otel-python-contrib`)
+
 ### Changed
 
 - **Always populate messages and tool arguments on Python objects** — `input_messages`, `output_messages`, and tool call `arguments` are now always set on `LLMInvocation`/`ToolCall` regardless of `OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT`. The emitter layer controls what reaches telemetry, enabling evaluators to access full content even in `NO_CONTENT` mode.
@@ -34,7 +40,7 @@ Initial release of `splunk-otel-instrumentation-openai` package.
 - Update tool call handling
   ([#135](https://github.com/signalfx/splunk-otel-python-contrib/pull/135))
 - Add suppression key handling
-  ([#155](https://github.com/signalfx/splunk-otel-python-contrib/pull/135))
+  ([#155](https://github.com/signalfx/splunk-otel-python-contrib/pull/155))
 - Move events/logs and metrics to handler-based emitters
   ([#158](https://github.com/signalfx/splunk-otel-python-contrib/pull/158))
 - Fix service tier attribute names: use `GEN_AI_OPENAI_REQUEST_SERVICE_TIER` for request

instrumentation-genai/opentelemetry-instrumentation-openai-v2/README.rst

@@ -3,8 +3,8 @@ OpenTelemetry OpenAI Instrumentation
 
 |pypi|
 
-.. |pypi| image:: https://badge.fury.io/py/opentelemetry-instrumentation-openai-v2.svg
-   :target: https://pypi.org/project/opentelemetry-instrumentation-openai-v2/
+.. |pypi| image:: https://badge.fury.io/py/splunk-otel-instrumentation-openai.svg
+   :target: https://pypi.org/project/splunk-otel-instrumentation-openai/
 
 This library allows tracing LLM requests and logging of messages made by the
 `OpenAI Python API library <https://pypi.org/project/openai/>`_. It also captures
@@ -40,7 +40,7 @@ If your application is already instrumented with OpenTelemetry, add this
 package to your requirements.
 ::
 
-    pip install opentelemetry-instrumentation-openai-v2
+    pip install splunk-otel-instrumentation-openai
 
 If you don't have an OpenAI application, yet, try our `examples <examples>`_
 which only need a valid OpenAI API key.
@@ -89,6 +89,24 @@ Message content such as the contents of the prompt, completion, function argumen
 are not captured by default. To capture message content as log events, set the environment variable
 `OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT` to `true`.
 
+See the `upstream OpenTelemetry documentation <https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation-genai/opentelemetry-instrumentation-openai-v2#enabling-message-content>`_ for more details.
+
+Suppressing nested instrumentation
+***********************************
+
+When using multiple instrumentations together (e.g., LangChain + OpenAI), the higher-level
+instrumentation automatically sets ``SUPPRESS_LANGUAGE_MODEL_INSTRUMENTATION_KEY`` in the
+OpenTelemetry context to prevent duplicate spans for the same underlying LLM call.
+
+This is handled transparently — **no user configuration is needed**. For example, when
+LangChain instrumentation is active alongside OpenAI instrumentation, you will see
+LangChain spans without redundant nested OpenAI spans.
+
+.. note::
+
+   This is not an environment variable and cannot be configured for zero-code instrumentation.
+   It is a context key managed programmatically by instrumentation libraries.
+
 Uninstrument
 ************
 
@@ -106,7 +124,7 @@ To uninstrument clients, call the uninstrument method:
 
 References
 ----------
-* `OpenTelemetry OpenAI Instrumentation <https://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation-genai/openai.html>`_
+* `Splunk OpenTelemetry OpenAI Instrumentation <https://github.com/signalfx/splunk-otel-python-contrib/tree/main/instrumentation-genai/opentelemetry-instrumentation-openai-v2>`_
 * `OpenTelemetry Project <https://opentelemetry.io/>`_
 * `OpenTelemetry Python Examples <https://github.com/open-telemetry/opentelemetry-python/tree/main/docs/examples>`_
 

instrumentation-genai/opentelemetry-instrumentation-openai-v2/pyproject.toml

@@ -35,8 +35,8 @@ instruments = [
 openai = "opentelemetry.instrumentation.openai_v2:OpenAIInstrumentor"
 
 [project.urls]
-Homepage = "https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation-genai/opentelemetry-instrumentation-openai-v2"
-Repository = "https://github.com/open-telemetry/opentelemetry-python-contrib"
+Homepage = "https://github.com/signalfx/splunk-otel-python-contrib/tree/main/instrumentation-genai/opentelemetry-instrumentation-openai-v2"
+Repository = "https://github.com/signalfx/splunk-otel-python-contrib"
 
 [tool.hatch.version]
 path = "src/opentelemetry/instrumentation/openai_v2/version.py"