Skip to content

DP-1.17: use per-flow OTG telemetry for tagged metrics polling - #6020

Open
dipchauh wants to merge 1 commit into
openconfig:mainfrom
nokia:dp1dot17
Open

DP-1.17: use per-flow OTG telemetry for tagged metrics polling#6020
dipchauh wants to merge 1 commit into
openconfig:mainfrom
nokia:dp1dot17

Conversation

@dipchauh

Copy link
Copy Markdown
Contributor

Replace FlowAny() with per-flow OTG telemetry when polling for tagged metrics, similar to other tests. This ensures tagged metrics are collected properly on reduced-scale Ixia cards (eg. Novus-R)

"This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia's intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind."

"This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia's intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind."
@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 DSCP transparency test to use per-flow OTG telemetry for collecting tagged metrics. By moving away from a broad global query, the test ensures reliable metric collection on hardware with limited scale, such as Novus-R cards, while maintaining existing validation logic.

Highlights

  • Telemetry Collection Optimization: Replaced the global FlowAny() telemetry query with per-flow queries to improve efficiency and compatibility with reduced-scale Ixia hardware.
  • Flow Name Resolution: Added logic to dynamically map DSCP values to specific queue names, enabling precise flow-based metric polling.
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.

@OpenConfigBot

Copy link
Copy Markdown

Pull Request Functional Test Report for #6020 / af595ab

Virtual Devices

Device Test Test Documentation Job Raw Log
Arista cEOS status
DP-1.17: DSCP Transparency with ECN
Cisco 8000E status
DP-1.17: DSCP Transparency with ECN
Cisco XRd status
DP-1.17: DSCP Transparency with ECN
Juniper ncPTX status
DP-1.17: DSCP Transparency with ECN
Nokia SR Linux status
DP-1.17: DSCP Transparency with ECN
Openconfig Lemming status
DP-1.17: DSCP Transparency with ECN

Hardware Devices

Device Test Test Documentation Raw Log
Arista status
DP-1.17: DSCP Transparency with ECN
Cisco status
DP-1.17: DSCP Transparency with ECN
Juniper status
DP-1.17: DSCP Transparency with ECN
Nokia status
DP-1.17: DSCP Transparency with ECN

Help

@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 optimizes the waitForAndGetTaggedMetrics function in dscp_transparency_test.go by querying telemetry for specific flow names instead of using a wildcard query for all flows. It maps expected metric IDs to specific queue names (such as BE1, BE0, AF1-4, NC1) to construct the target flow names, reducing the volume of telemetry data retrieved during the polling loop. There are no review comments, and I have no additional feedback to provide.

@dipchauh
dipchauh marked this pull request as ready for review September 10, 2026 21:37
@dipchauh
dipchauh requested a review from a team as a code owner September 10, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants