Skip to content

fix(telemetry): respect logPrompts flag in all API events#23964

Open
jonpjenkins wants to merge 1 commit intogoogle-gemini:mainfrom
jonpjenkins:fix-telemetry-privacy-issue-18979
Open

fix(telemetry): respect logPrompts flag in all API events#23964
jonpjenkins wants to merge 1 commit intogoogle-gemini:mainfrom
jonpjenkins:fix-telemetry-privacy-issue-18979

Conversation

@jonpjenkins
Copy link
Copy Markdown

Fixes #18979

@jonpjenkins jonpjenkins requested a review from a team as a code owner March 27, 2026 00:31
@google-cla
Copy link
Copy Markdown

google-cla Bot commented Mar 27, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 enhances privacy controls for telemetry by ensuring that sensitive prompt and response content is not included in logs unless explicitly permitted by the configuration. It modifies the telemetry event classes to conditionally include request and response attributes based on the 'logPrompts' setting and adds corresponding test cases to validate this behavior.

Highlights

  • Telemetry Privacy: Updated API request and response telemetry events to respect the 'logPrompts' configuration flag, ensuring sensitive prompt and response data is only logged when enabled.
  • Test Coverage: Added comprehensive unit tests to verify that request and response text attributes are correctly omitted from telemetry logs when prompt logging is disabled.
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.

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.

Copy link
Copy Markdown
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 updates the telemetry logging for API requests and responses to respect the logPrompts configuration. Specifically, request_text, response_text, and gen_ai.output.messages are now only included in telemetry attributes if prompt logging is enabled. Corresponding tests have been added and updated to verify this behavior. I have no feedback to provide.

@jonpjenkins jonpjenkins force-pushed the fix-telemetry-privacy-issue-18979 branch 2 times, most recently from e5914d5 to 6474624 Compare March 27, 2026 00:38
@jonpjenkins jonpjenkins force-pushed the fix-telemetry-privacy-issue-18979 branch from 6474624 to 0d19922 Compare March 27, 2026 00:38
@gemini-cli gemini-cli Bot added the area/security Issues related to security label Mar 27, 2026
@gemini-cli
Copy link
Copy Markdown
Contributor

gemini-cli Bot commented Apr 10, 2026

Hi there! Thank you for your interest in contributing to Gemini CLI.

To ensure we maintain high code quality and focus on our prioritized roadmap, we have updated our contribution policy (see Discussion #17383).

We only guarantee review and consideration of pull requests for issues that are explicitly labeled as 'help wanted'. All other community pull requests are subject to closure after 14 days if they do not align with our current focus areas. For this reason, we strongly recommend that contributors only submit pull requests against issues explicitly labeled as 'help-wanted'.

This pull request is being closed as it has been open for 14 days without a 'help wanted' designation. We encourage you to find and contribute to existing 'help wanted' issues in our backlog! Thank you for your understanding and for being part of our community!

@gemini-cli gemini-cli Bot closed this Apr 10, 2026
@galz10 galz10 reopened this Apr 28, 2026
@gemini-cli gemini-cli Bot added the help wanted We will accept PRs from all issues marked as "help wanted". Thanks for your support! label Apr 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/security Issues related to security help wanted We will accept PRs from all issues marked as "help wanted". Thanks for your support!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

User prompts included in api_request logs despite logPrompts=false

2 participants