Skip to content

gNMI-1.21: Register missing integrated-circuit resource utilization telemetry paths - #5792

Open
devansh-lodha wants to merge 2 commits into
openconfig:mainfrom
devansh-lodha:fix/integrated-circuit-utilization-telemetry
Open

gNMI-1.21: Register missing integrated-circuit resource utilization telemetry paths#5792
devansh-lodha wants to merge 2 commits into
openconfig:mainfrom
devansh-lodha:fix/integrated-circuit-utilization-telemetry

Conversation

@devansh-lodha

Copy link
Copy Markdown
Contributor

Fixes #5791

  • (M) feature/platform/integrated_circuit/otg_tests/utilization_test/README.md
    • Add /components/component/integrated-circuit/utilization/resources/resource/state/max-limit.
    • Add /components/component/integrated-circuit/utilization/resources/resource/state/used-threshold-upper.
    • Add /components/component/integrated-circuit/utilization/resources/resource/state/used-threshold-upper-clear.
    • Add /components/component/integrated-circuit/utilization/resources/resource/state/used-threshold-upper-exceeded.
    • Add valid non-empty System Utilization Canonical OC JSON.

@devansh-lodha
devansh-lodha requested a review from a team as a code owner July 29, 2026 07:47
@OpenConfigBot

OpenConfigBot commented Jul 29, 2026

Copy link
Copy Markdown

@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 updates the documentation and path coverage for integrated-circuit resource utilization telemetry. By registering additional OpenConfig paths and providing a canonical JSON example, it ensures better alignment with gNMI standards and improves the clarity of test requirements for hardware resource monitoring.

Highlights

  • Telemetry Path Registration: Added missing gNMI telemetry paths for integrated-circuit resource utilization, including max-limit, used-threshold-upper, used-threshold-upper-clear, and used-threshold-upper-exceeded.
  • Documentation Update: Included a valid non-empty System Utilization Canonical OC JSON example in the utilization test README to improve test documentation.
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 the 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 counterproductive. 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.

@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 updates the README.md for the integrated circuit utilization test. It adds a 'Canonical OC' section with a JSON example of the system utilization configuration and expands the list of covered OpenConfig paths to include several integrated-circuit utilization state paths (such as free, max-limit, used-threshold-upper, used-threshold-upper-clear, and used-threshold-upper-exceeded). There are no review comments, and I have no feedback to provide.

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.

gNMI-1.21: Missing integrated-circuit utilization telemetry state paths in README.md

2 participants