cisco Model-Driven Telemetry — Dynamic Subscription Management

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 SubscriptionMode Message This message informs the target about how to trigger notifications updates. The following is a SubscriptionMode message definition: enum SubscriptionMode { TARGET_DEFINED = 0; ON_CHANGE = 1; SAMPLE = 2; } Note Only SAMPLE and ON_CHANGE (from Cisco IOS XE Bengaluru 17.6.1) are supported. ON_CHANGE support is limited to certain model paths. To check whether a path supports ON_CHANGE, query the path in the Cisco-IOS-XE-MDT-capabilities-oper model.

For more information about the model, see the section, Displaying On-Change Subscription Capabilities, on page 29 . Notifications Message This message delivers telemetry data from the subscription target to the collector. The following is a Notifications message definition: message Notification { int64 timestamp = 1; Path prefix = 2; string alias = 3; repeated Update update = 4; repeated Path delete = 5; bool atomic = 6; } Timestamp, prefix, and update are supported. Note Dynamic Subscription Management This section describes how to create and delete dynamic subscriptions. Model-Driven Telemetry Dynamic Subscription Management Model-Driven Telemetry 12