Skip to content

Conversation

@vinoo999
Copy link

@vinoo999 vinoo999 commented Jan 8, 2026

Description

Support disabling OTEL instrumentation via the a2a-sdk using an environment variable OTEL_A2A_SDK_INSTRUMENTATION_ENABLED

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Follow the CONTRIBUTING Guide.
  • Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
    • Important Prefixes for release-please:
      • fix: which represents bug fixes, and correlates to a SemVer patch.
      • feat: represents a new feature, and correlates to a SemVer minor.
      • feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.
  • Ensure the tests and linter pass (Run bash scripts/format.sh from the repository root to format)
  • Appropriate docs were updated (if necessary)

Fixes #604 🦕

…s and xdist configuration to ensure module import tests can be run in the same group
@vinoo999 vinoo999 requested a review from a team as a code owner January 8, 2026 11:32
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @vinoo999, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a feature to disable telemetry instrumentation using an environment variable, providing more control over data collection. It also enhances the testing framework by adding pytest-xdist for parallel test execution and ensuring that telemetry tests run in isolation. The changes include modifications to the pyproject.toml file, the telemetry utility module, and the test suite.

Highlights

  • Telemetry Instrumentation Control: Adds the ability to disable OpenTelemetry instrumentation via the OTEL_A2A_SDK_INSTRUMENTATION_ENABLED environment variable.
  • Test Isolation: Introduces pytest-xdist and marks telemetry-related tests to run in an isolated group to prevent interference.
  • Dependency Updates: Updates uv.lock to include pytest-xdist and pyjwt as dependencies.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

StatusCode = _NoOp() # type: ignore

SpanKind = _SpanKind
SpanKind = _SpanKind # type: ignore
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was receiving unbound linting errors since i moved the assignment to line 132 rather than exception block.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a feature to disable OpenTelemetry instrumentation via the OTEL_A2A_SDK_INSTRUMENTATION_ENABLED environment variable. The implementation is solid, including comprehensive tests that cleverly reload the module to check the environment variable's effect. I've found one bug related to tracer initialization and have a couple of suggestions for improvement. One suggestion is to separate an unrelated dependency change into its own pull request to maintain focus. Overall, this is a great addition.

Configuration:
- Environment Variable Control: OpenTelemetry instrumentation can be
disabled using the `OTEL_INSTRUMENTATION_A2A_SDK_ENABLED` environment
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer that the default value for the flag is 0/false which are usually the defaults for unset values.

How about renaming it to A2A_DISABLE_OTEL_INSTRUMENTATION?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't feel too strongly on the name though but it is enabled in code by default.

it could be OTEL_INSTRUMENTATION_A2A_SDK_DISABLED but wrapping your head around 1 for the env var disabling instrumentation while 0 enabling it is awkward. I generally prefer to avoid negation env vars

addopts = "-ra --strict-markers --dist loadgroup"
markers = [
"asyncio: mark a test as a coroutine that should be run by pytest-asyncio",
"xdist_group: mark a test to run in a specific sequential group for isolation",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please explain why you need this extra dependency. Can we do without it?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new tests need to reload the telemetry module with different OTEL_INSTRUMENTATION_A2A_SDK_ENABLED environment variable values. The module-level code in telemetry.py checks this env var once at import time, so changing it mid-test-run doesn't work unless you reload the module. xdist prevents race conditions when modifying the module level code vars so that these tests don't set/re-set the env var accordingly.

This dependency is only added for dev is there an issue here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feat]: Support disabling A2A OTEL Instrumentation

3 participants