the gnmi input plugin should support the gRPC Keepalive configuration #15148
Labels
feature request
Requests for new plugin and for new features to existing plugins
Comments
retnuh
added
the
feature request
1 task
|
next steps: get final reviews in 15149, thanks again for the PR |
powersj
added a commit
to powersj/telegraf
that referenced
this issue
Apr 16, 2024
This is a simple PR to plumb through the keep alive settings for the gRPC connections used by the gnmi input plugin, see the related issue for more details. resolves: influxdata#15148
powersj
added a commit
to powersj/telegraf
that referenced
this issue
Apr 16, 2024
This is a simple PR to plumb through the keep alive settings for the gRPC connections used by the gnmi input plugin, see the related issue for more details. resolves: influxdata#15148 Co-authored-by: Hunter Kelly <[email protected]>
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use Case
When the service on the target end of a gnmi subscription becomes unavailable, "on change" gnmi subscriptions won't notice and won't attempt to reconnect until 2 hours after the last data was received.
The gRPC library already contains functionality to address these issues:
https://pkg.go.dev/google.golang.org/grpc/keepalive
Expected behavior
the gRPC library supports keep alive configuration to handle this appropriately; exposing this configuration will allow the telegraf end user to customize the behaviour of their gRPC connections.
Actual behavior
Currently there is no way to configure the keep alive behaviour of gRPC connections.
Additional info
No response
The text was updated successfully, but these errors were encountered: