Skip to content

gnmi on-change clarification #219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
osquitun wants to merge 2 commits into
base: master
Choose a base branch
from
Open

gnmi on-change clarification #219

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
95392c1
Update gnmi-specification.md
osquitun Jan 21, 2025
4040770
Merge pull request #1 from osquitun/osquitun-on-change-counter
osquitun Jan 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion rpc/gnmi/gnmi-specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1602,7 +1602,7 @@ with one of the following `modes`:
- For all `ON_CHANGE` subscriptions, the target MUST first generate updates
for all paths that match the subscription path(s), and transmit them.
Following this initial set of updates, updated values SHOULD only be
transmitted when their value changes.
transmitted when their value changes with the exception of rapidly changing counter types. Counter type values SHOULD be transmitted upon the initial subscription update and at each heartbeat_interval if one is specified.
- A heartbeat interval MAY be specified along with an "on change"
subscription - in this case, the value of the data item(s) MUST be re-sent
once per heartbeat interval regardless of whether the value has changed or
Expand Down