feat(telemetry): Ensure experiment IDs are included in OpenTelemetry logs

[kevin-ramdass]

Summary

This PR injects experiments.ids into all OpenTelemetry (OTel) events, ensuring experiment tracking parity with the existing Clearcut telemetry system.

Details

• Synchronous Injection: Updates getCommonAttributes in packages/core/src/telemetry/telemetryAttributes.ts to append available experiment IDs as the experiments.ids array attribute, aligning with OTel semantic conventions.
• Async Pre-loading: Wraps OTel emission for early lifecycle events (logCliConfiguration and logStartupStats in packages/core/src/telemetry/loggers.ts) with .then() blocks executing after config.getExperimentsAsync(). This guarantees that experiment configurations are loaded before emitting the payload.
• Test Suite Updates: Adds getExperiments() and getExperimentsAsync() static variables to the Config mocks across loggers.test.ts, sdk.test.ts, and sanitize.test.ts. Refactored early-event test cases to asynchronously await until process.nextTick resolves the logging promises.

Related Issues

Related to #12244

How to Validate

Enable OTEL logging and verify experiment ids are logged.

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello @kevin-ramdass, I'm Gemini Code Assist¹! 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 significantly enhances the OpenTelemetry logging capabilities by ensuring that experiment IDs are consistently captured and included in all telemetry events. The changes involve modifying the core telemetry attribute collection logic and introducing asynchronous handling for early-stage events to guarantee that experiment configurations are fully loaded before any relevant data is emitted. This brings OpenTelemetry tracking in line with the existing Clearcut system, providing a more comprehensive view of experiment participation in logs.

Highlights

• OpenTelemetry Experiment ID Integration: Integrated experiment IDs into all OpenTelemetry events to achieve parity with the existing Clearcut telemetry system, ensuring consistent tracking of experiment participation.
• Asynchronous Experiment Pre-loading: Implemented asynchronous pre-loading for experiment configurations, specifically for early lifecycle telemetry events (logCliConfiguration and logStartupStats), to guarantee that complete experiment data is available before events are emitted.
• Test Suite Enhancements: Updated test suites across loggers.test.ts, sdk.test.ts, and sanitize.test.ts to accommodate the new asynchronous experiment loading mechanism and mock the necessary getExperiments() and getExperimentsAsync() configuration properties.

Changelog

• packages/core/src/telemetry/loggers.test.ts
  • Updated logCliConfiguration test to be asynchronous.
  • Added getExperiments and getExperimentsAsync properties to various Config mock objects.
  • Introduced await new Promise(process.nextTick) to ensure asynchronous operations complete before assertions.
  • Updated Telemetry Buffering test to be asynchronous.
• packages/core/src/telemetry/loggers.ts
  • Modified logCliConfiguration to asynchronously wait for config.getExperimentsAsync() before emitting the log record.
  • Modified logStartupStats to asynchronously wait for config.getExperimentsAsync() before emitting the log record.
• packages/core/src/telemetry/sanitize.test.ts
  • Added getExperiments and getExperimentsAsync properties to the createMockConfig function.
• packages/core/src/telemetry/sdk.test.ts
  • Added getExperiments and getExperimentsAsync properties to the mockConfig in the beforeEach block.
  • Added a setTimeout await in initializeTelemetry test to ensure asynchronous initialization completes.
• packages/core/src/telemetry/telemetryAttributes.ts
  • Updated getCommonAttributes to retrieve experiment IDs from the configuration and conditionally include them in the OpenTelemetry attributes if available.

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. ↩

[gemini-cli]

Hi @kevin-ramdass, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.

We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines.

Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.

Thank you for your understanding and for being a part of our community!

[gemini-code-assist]

Code Review

The pull request successfully integrates experiment IDs into OpenTelemetry logs, ensuring parity with the existing Clearcut telemetry system. The changes correctly introduce asynchronous pre-loading of experiment configurations for early lifecycle events and update the test suite to accommodate this new asynchronous behavior. However, the review identified potential issues with unhandled promise rejections in telemetry logging, which should be addressed for application stability. Overall, the modifications are well-aligned with the stated objectives, pending resolution of the identified asynchronous issues.

[github-actions]

Size Change: +506 B (0%)

Total Size: 23.9 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.9 MB	+506 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}