openconfig-telemetry

openconfig-version: 0.5.1

Description

Data model which creates the configuration for the telemetry systems and functions on the device.

Imports

openconfig-inet-types
openconfig-extensions
openconfig-telemetry-types

Data elements

/
telemetry-system

description:
Top level configuration and state for the device's telemetry system.

nodetype: container (rw)

/telemetry-system/
sensor-groups

description:
Top level container for sensor-groups.

nodetype: container (rw)

/telemetry-system/sensor-groups/
sensor-group

description:
List of telemetry sensory groups on the local system, where a sensor grouping represents a resuable grouping of multiple paths and exclude filters.

nodetype: list (rw)

list keys: [sensor-group-id]

/telemetry-system/sensor-groups/sensor-group/
sensor-group-id

description:
Reference to the name or identifier of the sensor grouping

nodetype: leaf (list key) (rw)

type: leafref

  • path reference: ../config/sensor-group-id

/telemetry-system/sensor-groups/sensor-group/
config

description:
Configuration parameters relating to the telemetry sensor grouping

nodetype: container (rw)

/telemetry-system/sensor-groups/sensor-group/config/
sensor-group-id

description:
Name or identifier for the sensor group itself. Will be referenced by other configuration specifying a sensor group

nodetype: leaf (rw)

type: string

/telemetry-system/sensor-groups/sensor-group/
state

description:
State information relating to the telemetry sensor group

nodetype: container (ro)

/telemetry-system/sensor-groups/sensor-group/state/
sensor-group-id

description:
Name or identifier for the sensor group itself. Will be referenced by other configuration specifying a sensor group

nodetype: leaf (ro)

type: string

/telemetry-system/sensor-groups/sensor-group/
sensor-paths

description:
Top level container to hold a set of sensor paths grouped together

nodetype: container (rw)

/telemetry-system/sensor-groups/sensor-group/sensor-paths/
sensor-path

description:
List of paths in the model which together comprise a sensor grouping. Filters for each path to exclude items are also provided.

nodetype: list (rw)

list keys: [path]

/telemetry-system/sensor-groups/sensor-group/sensor-paths/sensor-path/
path

description:
Reference to the path of interest

nodetype: leaf (list key) (rw)

type: leafref

  • path reference: ../config/path

/telemetry-system/sensor-groups/sensor-group/sensor-paths/sensor-path/
config

description:
Configuration parameters to configure a set of data model paths as a sensor grouping

nodetype: container (rw)

/telemetry-system/sensor-groups/sensor-group/sensor-paths/sensor-path/config/
path

description:
Path to a section of operational state of interest (the sensor).

nodetype: leaf (rw)

type: string

/telemetry-system/sensor-groups/sensor-group/sensor-paths/sensor-path/config/
exclude-filter

description:
Filter to exclude certain values out of the state values

nodetype: leaf (rw)

type: string

/telemetry-system/sensor-groups/sensor-group/sensor-paths/sensor-path/
state

description:
Configuration parameters to configure a set of data model paths as a sensor grouping

nodetype: container (ro)

/telemetry-system/sensor-groups/sensor-group/sensor-paths/sensor-path/state/
path

description:
Path to a section of operational state of interest (the sensor).

nodetype: leaf (ro)

type: string

/telemetry-system/sensor-groups/sensor-group/sensor-paths/sensor-path/state/
exclude-filter

description:
Filter to exclude certain values out of the state values

nodetype: leaf (ro)

type: string

/telemetry-system/
destination-groups

description:
Top level container for destination group configuration and state.

nodetype: container (rw)

/telemetry-system/destination-groups/
destination-group

description:
List of destination-groups. Destination groups allow the reuse of common telemetry destinations across the telemetry configuration. An operator references a set of destinations via the configurable destination-group-identifier. A destination group may contain one or more telemetry destinations

nodetype: list (rw)

list keys: [group-id]

/telemetry-system/destination-groups/destination-group/
group-id

description:
Unique identifier for the destination group

nodetype: leaf (list key) (rw)

type: leafref

  • path reference: ../config/group-id

/telemetry-system/destination-groups/destination-group/
config

description:
Top level config container for destination groups

nodetype: container (rw)

/telemetry-system/destination-groups/destination-group/config/
group-id

description:
Unique identifier for the destination group

nodetype: leaf (rw)

type: string

/telemetry-system/destination-groups/destination-group/
state

description:
Top level state container for destination groups

nodetype: container (ro)

/telemetry-system/destination-groups/destination-group/state/
group-id

description:
Unique identifier for destination group

nodetype: leaf (ro)

type: string

/telemetry-system/destination-groups/destination-group/
destinations

description:
The destination container lists the destination information such as IP address and port of the telemetry messages from the network element.

nodetype: container (rw)

/telemetry-system/destination-groups/destination-group/destinations/
destination

description:
List of telemetry stream destinations

nodetype: list (rw)

list keys: [destination-address] [destination-port]

/telemetry-system/destination-groups/destination-group/destinations/destination/
destination-address

description:
Reference to the destination address of the telemetry stream

nodetype: leaf (list key) (rw)

type: leafref

  • path reference: ../config/destination-address

/telemetry-system/destination-groups/destination-group/destinations/destination/
destination-port

description:
Reference to the port number of the stream destination

nodetype: leaf (list key) (rw)

type: leafref

  • path reference: ../config/destination-port

/telemetry-system/destination-groups/destination-group/destinations/destination/
config

description:
Configuration parameters relating to telemetry destinations

nodetype: container (rw)

/telemetry-system/destination-groups/destination-group/destinations/destination/config/
destination-address

description:
IP address of the telemetry stream destination

nodetype: leaf (rw)

type: oc-inet:ip-address

/telemetry-system/destination-groups/destination-group/destinations/destination/config/
destination-port

description:
Protocol (udp or tcp) port number for the telemetry stream destination

nodetype: leaf (rw)

type: uint16

/telemetry-system/destination-groups/destination-group/destinations/destination/
state

description:
State information associated with telemetry destinations

nodetype: container (ro)

/telemetry-system/destination-groups/destination-group/destinations/destination/state/
destination-address

description:
IP address of the telemetry stream destination

nodetype: leaf (ro)

type: oc-inet:ip-address

/telemetry-system/destination-groups/destination-group/destinations/destination/state/
destination-port

description:
Protocol (udp or tcp) port number for the telemetry stream destination

nodetype: leaf (ro)

type: uint16

/telemetry-system/
subscriptions

description:
This container holds information for both persistent and dynamic telemetry subscriptions.

nodetype: container (rw)

/telemetry-system/subscriptions/
persistent-subscriptions

description:
This container holds information relating to persistent telemetry subscriptions. A persistent telemetry subscription is configued locally on the device through configuration, and is persistent across device restarts or other redundancy changes.

nodetype: container (rw)

/telemetry-system/subscriptions/persistent-subscriptions/
persistent-subscription

description:
List of telemetry subscriptions. A telemetry subscription consists of a set of collection destinations, stream attributes, and associated paths to state information in the model (sensor data)

nodetype: list (rw)

list keys: [name]

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/
name

description:
Reference to the identifier of the subscription itself. The id will be the handle to refer to the subscription once created

nodetype: leaf (list key) (rw)

type: leafref

  • path reference: ../config/name

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/
config

description:
Config parameters relating to the telemetry subscriptions on the local device

nodetype: container (rw)

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/config/
name

description:
User configured identifier of the telemetry subscription. This value is used primarily for subscriptions configured locally on the network element.

nodetype: leaf (rw)

type: string

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/config/
local-source-address

description:
The IP address which will be the source of packets from the device to a telemetry collector destination.

nodetype: leaf (rw)

type: oc-inet:ip-address

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/config/
originated-qos-marking

description:
DSCP marking of packets generated by the telemetry subsystem on the network device.

nodetype: leaf (rw)

type: oc-inet:dscp

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/config/
protocol

description:
Selection of the transport protocol for the telemetry stream.

nodetype: leaf (rw)

type: identityref

  • base: oc-telemetry-types:STREAM_PROTOCOL

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/config/
encoding

description:
Selection of the specific encoding or RPC framework for telemetry messages to and from the network element.

nodetype: leaf (rw)

type: identityref

  • base: oc-telemetry-types:DATA_ENCODING_METHOD

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/
state

description:
State parameters relating to the telemetry subscriptions on the local device

nodetype: container (ro)

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/state/
name

description:
User configured identifier of the telemetry subscription. This value is used primarily for subscriptions configured locally on the network element.

nodetype: leaf (ro)

type: string

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/state/
id

description:
System generated identifer of the telemetry subscription.

nodetype: leaf (ro)

type: uint64

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/state/
local-source-address

description:
The IP address which will be the source of packets from the device to a telemetry collector destination.

nodetype: leaf (ro)

type: oc-inet:ip-address

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/state/
originated-qos-marking

description:
DSCP marking of packets generated by the telemetry subsystem on the network device.

nodetype: leaf (ro)

type: oc-inet:dscp

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/state/
protocol

description:
Selection of the transport protocol for the telemetry stream.

nodetype: leaf (ro)

type: identityref

  • base: oc-telemetry-types:STREAM_PROTOCOL

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/state/
encoding

description:
Selection of the specific encoding or RPC framework for telemetry messages to and from the network element.

nodetype: leaf (ro)

type: identityref

  • base: oc-telemetry-types:DATA_ENCODING_METHOD

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/
sensor-profiles

description:
A sensor profile is a set of sensor groups or individual sensor paths which are associated with a telemetry subscription. This is the source of the telemetry data for the subscription to send to the defined collectors.

nodetype: container (rw)

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/
sensor-profile

description:
List of telemetry sensor groups used in the subscription

nodetype: list (rw)

list keys: [sensor-group]

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/
sensor-group

description:
Reference to the telemetry sensor group name

nodetype: leaf (list key) (rw)

type: leafref

  • path reference: ../config/sensor-group

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/
config

description:
Configuration parameters related to the sensor profile for a subscription

nodetype: container (rw)

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/config/
sensor-group

description:
Reference to the sensor group which is used in the profile

nodetype: leaf (rw)

type: leafref

  • path reference: ../../../../../../../sensor-groups/sensor-group/config/sensor-group-id

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/config/
sample-interval

description:
Time in milliseconds between the device's sample of a telemetry data source. For example, setting this to 100 would require the local device to collect the telemetry data every 100 milliseconds. There can be latency or jitter in transmitting the data, but the sample must occur at the specified interval. The timestamp must reflect the actual time when the data was sampled, not simply the previous sample timestamp + sample-interval. If sample-interval is set to 0, the telemetry sensor becomes event based. The sensor must then emit data upon every change of the underlying data source.

nodetype: leaf (rw)

type: uint64

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/config/
heartbeat-interval

description:
Maximum time interval in seconds that may pass between updates from a device to a telemetry collector. If this interval expires, but there is no updated data to send (such as if suppress_updates has been configured), the device must send a telemetry message to the collector.

nodetype: leaf (rw)

type: uint64

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/config/
suppress-redundant

description:
Boolean flag to control suppression of redundant telemetry updates to the collector platform. If this flag is set to TRUE, then the collector will only send an update at the configured interval if a subscribed data value has changed. Otherwise, the device will not send an update to the collector until expiration of the heartbeat interval.

nodetype: leaf (rw)

type: boolean

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/
state

description:
State information relating to the sensor profile for a subscription

nodetype: container (ro)

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/state/
sensor-group

description:
Reference to the sensor group which is used in the profile

nodetype: leaf (ro)

type: leafref

  • path reference: ../../../../../../../sensor-groups/sensor-group/config/sensor-group-id

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/state/
sample-interval

description:
Time in milliseconds between the device's sample of a telemetry data source. For example, setting this to 100 would require the local device to collect the telemetry data every 100 milliseconds. There can be latency or jitter in transmitting the data, but the sample must occur at the specified interval. The timestamp must reflect the actual time when the data was sampled, not simply the previous sample timestamp + sample-interval. If sample-interval is set to 0, the telemetry sensor becomes event based. The sensor must then emit data upon every change of the underlying data source.

nodetype: leaf (ro)

type: uint64

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/state/
heartbeat-interval

description:
Maximum time interval in seconds that may pass between updates from a device to a telemetry collector. If this interval expires, but there is no updated data to send (such as if suppress_updates has been configured), the device must send a telemetry message to the collector.

nodetype: leaf (ro)

type: uint64

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/sensor-profiles/sensor-profile/state/
suppress-redundant

description:
Boolean flag to control suppression of redundant telemetry updates to the collector platform. If this flag is set to TRUE, then the collector will only send an update at the configured interval if a subscribed data value has changed. Otherwise, the device will not send an update to the collector until expiration of the heartbeat interval.

nodetype: leaf (ro)

type: boolean

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/
destination-groups

description:
A subscription may specify destination addresses. If the subscription supplies destination addresses, the network element will be the initiator of the telemetry streaming, sending it to the destination(s) specified. If the destination set is omitted, the subscription preconfigures certain elements such as paths and sample intervals under a specified subscription ID. In this case, the network element will NOT initiate an outbound connection for telemetry, but will wait for an inbound connection from a network management system. It is expected that the network management system connecting to the network element will reference the preconfigured subscription ID when initiating a subscription.

nodetype: container (rw)

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/destination-groups/
destination-group

description:
Identifier of the previously defined destination group

nodetype: list (rw)

list keys: [group-id]

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/destination-groups/destination-group/
group-id

description:
The destination group id references a configured group of destinations for the telemetry stream.

nodetype: leaf (list key) (rw)

type: leafref

  • path reference: ../config/group-id

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/destination-groups/destination-group/
config

description:
Configuration parameters related to telemetry destinations.

nodetype: container (rw)

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/destination-groups/destination-group/config/
group-id

description:
The destination group id references a reusable group of destination addresses and ports for the telemetry stream.

nodetype: leaf (rw)

type: leafref

  • path reference: ../../../../../../../destination-groups/destination-group/group-id

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/destination-groups/destination-group/
state

description:
State information related to telemetry destinations

nodetype: container (ro)

/telemetry-system/subscriptions/persistent-subscriptions/persistent-subscription/destination-groups/destination-group/state/
group-id

description:
The destination group id references a reusable group of destination addresses and ports for the telemetry stream.

nodetype: leaf (ro)

type: leafref

  • path reference: ../../../../../../../destination-groups/destination-group/group-id

/telemetry-system/subscriptions/
dynamic-subscriptions

description:
This container holds information relating to dynamic telemetry subscriptions. A dynamic subscription is typically configured through an RPC channel, and does not persist across device restarts, or if the RPC channel is reset or otherwise torn down.

nodetype: container (rw)

/telemetry-system/subscriptions/dynamic-subscriptions/
dynamic-subscription

description:
List representation of telemetry subscriptions that are configured via an inline RPC, otherwise known as dynamic telemetry subscriptions.

nodetype: list (ro)

list keys: [id]

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/
id

description:
Reference to the identifier of the subscription itself. The id will be the handle to refer to the subscription once created

nodetype: leaf (list key) (ro)

type: leafref

  • path reference: ../state/id

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/
state

description:
State information relating to dynamic telemetry subscriptions.

nodetype: container (ro)

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
id

description:
System generated identifer of the telemetry subscription.

nodetype: leaf (ro)

type: uint64

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
destination-address

description:
IP address of the telemetry stream destination

nodetype: leaf (ro)

type: oc-inet:ip-address

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
destination-port

description:
Protocol (udp or tcp) port number for the telemetry stream destination

nodetype: leaf (ro)

type: uint16

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
sample-interval

description:
Time in milliseconds between the device's sample of a telemetry data source. For example, setting this to 100 would require the local device to collect the telemetry data every 100 milliseconds. There can be latency or jitter in transmitting the data, but the sample must occur at the specified interval. The timestamp must reflect the actual time when the data was sampled, not simply the previous sample timestamp + sample-interval. If sample-interval is set to 0, the telemetry sensor becomes event based. The sensor must then emit data upon every change of the underlying data source.

nodetype: leaf (ro)

type: uint64

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
heartbeat-interval

description:
Maximum time interval in seconds that may pass between updates from a device to a telemetry collector. If this interval expires, but there is no updated data to send (such as if suppress_updates has been configured), the device must send a telemetry message to the collector.

nodetype: leaf (ro)

type: uint64

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
suppress-redundant

description:
Boolean flag to control suppression of redundant telemetry updates to the collector platform. If this flag is set to TRUE, then the collector will only send an update at the configured interval if a subscribed data value has changed. Otherwise, the device will not send an update to the collector until expiration of the heartbeat interval.

nodetype: leaf (ro)

type: boolean

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
originated-qos-marking

description:
DSCP marking of packets generated by the telemetry subsystem on the network device.

nodetype: leaf (ro)

type: oc-inet:dscp

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
protocol

description:
Selection of the transport protocol for the telemetry stream.

nodetype: leaf (ro)

type: identityref

  • base: oc-telemetry-types:STREAM_PROTOCOL

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/state/
encoding

description:
Selection of the specific encoding or RPC framework for telemetry messages to and from the network element.

nodetype: leaf (ro)

type: identityref

  • base: oc-telemetry-types:DATA_ENCODING_METHOD

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/
sensor-paths

description:
Top level container to hold a set of sensor paths grouped together

nodetype: container (ro)

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/sensor-paths/
sensor-path

description:
List of paths in the model which together comprise a sensor grouping. Filters for each path to exclude items are also provided.

nodetype: list (ro)

list keys: [path]

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/sensor-paths/sensor-path/
path

description:
Reference to the path of interest

nodetype: leaf (list key) (ro)

type: leafref

  • path reference: ../state/path

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/sensor-paths/sensor-path/
state

description:
State information for a dynamic subscription's paths of interest

nodetype: container (ro)

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/sensor-paths/sensor-path/state/
path

description:
Path to a section of operational state of interest (the sensor).

nodetype: leaf (ro)

type: string

/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription/sensor-paths/sensor-path/state/
exclude-filter

description:
Filter to exclude certain values out of the state values

nodetype: leaf (ro)

type: string