Skip to content
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.

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

Feat(eos_cli_config_gen): Add support for changing the notification timestamp mode for gnmi #1532

Closed
1 task done
noredistribution opened this issue Feb 21, 2022 · 0 comments · Fixed by #1533
Closed
1 task done
Assignees
Labels
type: enhancement New feature or request

Comments

@noredistribution
Copy link
Contributor

Enhancement summary

In 4.27.0F we've added support for changing the notification timestamp from the last-change-time (GNMI spec) to send-time (outside of spec) to support (legacy) systems that don't keep track of the last known state of a counter

Which component of AVD is impacted

eos_cli_config_gen

Use case example

folks who setup streaming via telegraf or any gnmi client to influx or other dbs and plot graphs with grafana won't see states outside of the selected range if that state has not changed for a long time, even if sampling mode is configured, as other systems are not like CloudVision which keeps track of the last known state of each counter...

Describe the solution you would like

we have a new cli "notification timestamp send-time" that can override the ts of the notifications everytime we stream it even if they did not change
ref: https://aristanetworks.github.io/openmgmt/configuration/openconfig/#telemetry-timestamps

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

  • I agree to follow this project's Code of Conduct
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
1 participant