[Telemetry] Add support to collect modules used in blueprint#5534
Conversation
Summary of ChangesHello, 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 telemetry support for tracking modules utilized within blueprints. It includes logic to identify and categorize modules as either standard (based on the official toolkit release) or custom, ensuring that sensitive or proprietary module paths are not exposed while still providing visibility into usage patterns. Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces telemetry for tracking modules used in blueprints by fetching a list of official modules from the GitHub API. Key changes include renaming GetAllModules to GetAllBpModules, implementing the GetPredefinedModules function, and updating the telemetry collector. Feedback focuses on a critical issue where a synchronous network request is made while holding a mutex lock, which could block operations. Additionally, the reviewer noted that errors from the GitHub API are currently ignored and suggested optimizations for the getBpModulesList function to reduce unnecessary allocations.
Repository rule violations found
86600d1
into
GoogleCloudPlatform:develop
This pull request introduces telemetry support for tracking modules utilized within blueprints. It includes logic to identify and categorize modules as either standard (based on the official toolkit release) or custom, ensuring that sensitive or proprietary module paths are not exposed while still providing visibility into usage patterns.
Changes:
KINDLY NOTE THAT TELEMETRY DATA IS NOT BEING COLLECTED YET.