} Path prefix (only explicit element names), Subscription subscription, Mode mode STREAM, and Encoding encoding IETF_JSON are supported. Note Prefix Message A valid subscription list may or may not contain a filled in prefix, composed of the shared (across all requested subscriptions) portion of the xPath. message Path { repeated string element = 1; [ deprecated ] string origin = 2; repeated PathElem elem = 3; optional string target = 4; } Origin (supported values are “” and “openconfig”), elem (supported element name is prefix-free), and target are supported. Note Subscription Message This message generically describes a set of data that is to be subscribed to by a client.
It contains a path,and attributes used to govern the notification behaviors. The following is a Subscription message definition: message Subscription { Path path = 1; SubscriptionMode mode = 2; uint64 sample_interval = 3; bool suppress_redundant = 4; uint64 heartbeat_interval = 5; } Path path, SubscriptionMode mode, Uint64 sample_interval, and Uint64 heartbeat_interval (only if the value is set to 0) are supported. Note Path Message A valid subscription contains a filled in path, which when added to the prefix associated with the subscription list constitutes a full qualified path. The following is a Path message definition:
message Path { repeated string element = 1; [ deprecated ] Model-Driven Telemetry Service gNMI Model-Driven Telemetry 11