Skip to content

[Telemetry] Add support to identify if user is internal or external#5503

Merged
kadupoornima merged 14 commits into
GoogleCloudPlatform:developfrom
kadupoornima:telemetry-7
Apr 23, 2026
Merged

[Telemetry] Add support to identify if user is internal or external#5503
kadupoornima merged 14 commits into
GoogleCloudPlatform:developfrom
kadupoornima:telemetry-7

Conversation

@kadupoornima

@kadupoornima kadupoornima commented Apr 15, 2026

Copy link
Copy Markdown
Contributor

This pull request enhances the Cluster Toolkit Telemetry system by introducing functionality to distinguish between internal and external users. By detecting specific Google-related account configurations and developer tools, the system can now tag events with an IsGoogler flag, enabling better analysis of tool usage patterns across different user segments.

Changes:

  • Telemetry Enhancement: Added a new IsGoogler boolean field to the concord event in telemetry to identify if the user is an internal Google user or not.
  • Internal User Detection: Implemented logic to detect internal users by checking for @google.com gcloud accounts and the presence of internal developer binaries.
  • Performance Optimization: Optimized the detection order to prioritize checking for local binaries before spawning a gcloud process.

KINDLY NOTE THAT TELEMETRY DATA IS NOT BEING COLLECTED YET.

@kadupoornima kadupoornima added the release-improvements Added to release notes under the "Improvements" heading. label Apr 15, 2026
@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 introduces functionality to distinguish between internal and external users within the telemetry data. By detecting specific Google-related account configurations and developer tools, the system can now tag events with an 'IsGoogler' flag, enabling better analysis of tool usage patterns across different user segments.

Highlights

  • Telemetry Enhancement: Added a new field 'IsGoogler' to the telemetry collector to identify if the user is an internal Google employee.
  • Internal User Detection: Implemented logic to detect internal users by checking for '@google.com' gcloud accounts and the presence of internal tools like 'gcert' or 'prodaccess'.
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.

@kadupoornima kadupoornima changed the title [Telemetry] Add support to identify if user is an internal user [Telemetry] Add support to identify if user is internal or external Apr 15, 2026

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

Copy link
Copy Markdown
Contributor

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 mechanism to identify internal Google users by checking the active gcloud account and the presence of internal developer tools. The review feedback suggests optimizing the check order for better performance and adding the --quiet flag to the gcloud command to prevent potential execution hangs.

Comment thread pkg/telemetry/collector.go Outdated
Comment thread pkg/telemetry/collector_util.go Outdated
kadupoornima and others added 3 commits April 15, 2026 07:05
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@kadupoornima

Copy link
Copy Markdown
Contributor Author

/gemini summary

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

This pull request introduces functionality to distinguish between internal and external users within the telemetry data. By detecting specific Google-related account configurations and developer tools, the system can now tag events with an 'IsGoogler' flag, enabling better analysis of tool usage patterns across different user segments.

Highlights

  • Telemetry Enhancement: Added a new 'IsGoogler' boolean field to the telemetry collector to identify if the user is an internal Google employee.
  • Internal User Detection: Implemented logic to detect internal users by checking for '@google.com' gcloud accounts and the presence of internal developer binaries like 'gcert' or 'prodaccess'.
  • Performance Optimization: Optimized the detection order to prioritize checking for local binaries before spawning a gcloud process.
Activity
  • Gemini Code Assist provided initial feedback suggesting performance optimizations and command flag improvements.
  • The author acknowledged the feedback and implemented the suggested changes.
  • The author requested a summary of the pull request.

@kadupoornima kadupoornima marked this pull request as ready for review April 21, 2026 08:20
@kadupoornima kadupoornima requested a review from a team as a code owner April 21, 2026 08:20
@kadupoornima

Copy link
Copy Markdown
Contributor Author

/gemini summary

@kadupoornima

Copy link
Copy Markdown
Contributor Author

/gemini review

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

This pull request enhances the Cluster Toolkit Telemetry system by introducing functionality to distinguish between internal and external users. By detecting specific Google-related account configurations and developer tools, the system can now tag events with an 'IsGoogler' flag, enabling better analysis of tool usage patterns across different user segments.

Highlights

  • Telemetry Enhancement: Added a new 'IsGoogler' boolean field to the concord event in telemetry to identify if the user is an internal Google user or not.
  • Internal User Detection: Implemented logic to detect internal users by checking for '@google.com' gcloud accounts and the presence of internal developer binaries.
  • Performance Optimization: Optimized the detection order to prioritize checking for local binaries before spawning a gcloud process.
Activity
  • Gemini Code Assist provided initial feedback suggesting performance optimizations and command flag improvements.
  • The author acknowledged the feedback and implemented the suggested changes.
  • The author requested a summary of the pull request.

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

Copy link
Copy Markdown
Contributor

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 mechanism to identify internal Google users and service accounts for telemetry purposes. It implements checks for Application Default Credentials and falls back to the gcloud CLI to determine the authenticated account. Feedback focuses on improving performance and reliability by checking for internal developer binaries before spawning external processes, implementing timeouts for shell commands, and optimizing email domain verification by replacing inefficient regex matching with string suffix checks.

Comment thread pkg/telemetry/collector.go
Comment thread pkg/telemetry/collector.go Outdated
Comment thread pkg/telemetry/collector_util.go Outdated
@kadupoornima kadupoornima enabled auto-merge (squash) April 21, 2026 08:53

@SwarnaBharathiMantena SwarnaBharathiMantena left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM!
Discussed offline about service accounts to consider as internal users.

@kadupoornima kadupoornima merged commit ad06168 into GoogleCloudPlatform:develop Apr 23, 2026
12 of 77 checks passed
@kadupoornima kadupoornima deleted the telemetry-7 branch April 23, 2026 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-improvements Added to release notes under the "Improvements" heading.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants