JTI OpenConfig Telemetry and VictoriaMetrics Integration

Input and output integration overview

The JTI OpenConfig Telemetry plugin allows users to collect real-time telemetry data from devices running Juniper’s implementation of the OpenConfig model, leveraging the Junos Telemetry Interface for efficient data retrieval.

This plugin enables Telegraf to efficiently write metrics directly into VictoriaMetrics using the InfluxDB line protocol, leveraging the performance and scalability features of VictoriaMetrics for large-scale time-series data.

Integration details

JTI OpenConfig Telemetry

This plugin reads data from Juniper Networks’ OpenConfig telemetry implementation using the Junos Telemetry Interface (JTI). OpenConfig is an initiative aimed at enabling standardized and open network device telemetry through a common model for various devices and protocols. The JTI allows for the collection of this telemetry data in a real-time manner from various sensors defined within the configuration. Configurable parameters for this plugin include the ability to specify device addresses, authentication credentials, sampling frequency, and multiple sensors with potentially different reporting rates. The plugin uniquely handles time-stamping either through the collection time or the timestamp provided in the data, allowing for flexibility in how data is processed. Given its support for TLS for secure communication, the plugin is well-suited for integration into both traditional and modern network management systems, enhancing visibility into network performance and reliability.

VictoriaMetrics

VictoriaMetrics supports direct ingestion of metrics in the InfluxDB line protocol, making this plugin ideal for efficient real-time metric storage and retrieval. The integration combines Telegraf’s extensive metric collection capabilities with VictoriaMetrics’ optimized storage and querying features, including compression, fast ingestion rates, and efficient disk utilization. Ideal for cloud-native and large-scale monitoring scenarios, this plugin offers simplicity, robust performance, and high reliability, enabling advanced operational insights and long-term storage solutions for large volumes of metrics.

Configuration

JTI OpenConfig Telemetry

[[inputs.jti_openconfig_telemetry]]
  ## List of device addresses to collect telemetry from
  servers = ["localhost:1883"]

  ## Authentication details. Username and password are must if device expects
  ## authentication. Client ID must be unique when connecting from multiple instances
  ## of telegraf to the same device
  username = "user"
  password = "pass"
  client_id = "telegraf"

  ## Frequency to get data
  sample_frequency = "1000ms"

  ## Sensors to subscribe for
  ## A identifier for each sensor can be provided in path by separating with space
  ## Else sensor path will be used as identifier
  ## When identifier is used, we can provide a list of space separated sensors.
  ## A single subscription will be created with all these sensors and data will
  ## be saved to measurement with this identifier name
  sensors = [
   "/interfaces/",
   "collection /components/ /lldp",
  ]

  ## We allow specifying sensor group level reporting rate. To do this, specify the
  ## reporting rate in Duration at the beginning of sensor paths / collection
  ## name. For entries without reporting rate, we use configured sample frequency
  sensors = [
   "1000ms customReporting /interfaces /lldp",
   "2000ms collection /components",
   "/interfaces",
  ]

  ## Timestamp Source
  ## Set to 'collection' for time of collection, and 'data' for using the time
  ## provided by the _timestamp field.
  # timestamp_source = "collection"

  ## Optional TLS Config
  # enable_tls = false
  # tls_ca = "/etc/telegraf/ca.pem"
  # tls_cert = "/etc/telegraf/cert.pem"
  # tls_key = "/etc/telegraf/key.pem"
  ## Minimal TLS version to accept by the client
  # tls_min_version = "TLS12"
  ## Use TLS but skip chain & host verification
  # insecure_skip_verify = false

  ## Delay between retry attempts of failed RPC calls or streams. Defaults to 1000ms.
  ## Failed streams/calls will not be retried if 0 is provided
  retry_delay = "1000ms"

  ## Period for sending keep-alive packets on idle connections
  ## This is helpful to identify broken connections to the server
  # keep_alive_period = "10s"

  ## To treat all string values as tags, set this to true
  str_as_tags = false

VictoriaMetrics

[[outputs.influxdb]]
  ## URL of the VictoriaMetrics write endpoint
  urls = ["http://localhost:8428"]

  ## VictoriaMetrics accepts InfluxDB line protocol directly
  database = "db_name"

  ## Optional authentication
  # username = "username"
  # password = "password"
  # skip_database_creation = true
  # exclude_retention_policy_tag = true
  # content_encoding = "gzip"

  ## Timeout for HTTP requests
  timeout = "5s"

  ## Optional TLS configuration
  # tls_ca = "/path/to/ca.pem"
  # tls_cert = "/path/to/cert.pem"
  # tls_key = "/path/to/key.pem"
  # insecure_skip_verify = false

Input and output integration examples

JTI OpenConfig Telemetry

1. Network Performance Monitoring: Use the JTI OpenConfig Telemetry plugin to monitor network performance metrics from multiple Juniper devices in real-time. By configuring various sensors, operators can gain insights into interface performance, traffic patterns, and error rates, allowing for proactive troubleshooting and optimization of the network.

2. Automated Fault Detection: Integrate the telemetry data collected via this plugin with a fault detection system that triggers alerts based on predefined thresholds. For example, when a specific sensor indicates a fault or threshold breach, automated scripts can be initiated to remediate the situation, dramatically improving response times.

3. Historical Performance Analysis: By forwarding the collected telemetry data into a time-series database, organizations can perform historical analysis on network performance. This enables teams to identify trends over time, spot anomalies, and make more informed decisions regarding network capacity planning and resource allocation.

4. Real-Time Dashboards for Network Operations: Leverage the real-time data gathered through this plugin to power visualization dashboards that provide network operators with live insights into performance metrics. This facilitates better operational awareness and quicker decision-making during critical events.

VictoriaMetrics

1. Cloud-Native Application Monitoring: Stream metrics from microservices deployed on Kubernetes directly into VictoriaMetrics. By centralizing metrics, organizations can perform real-time monitoring, rapid anomaly detection, and seamless scalability across dynamically evolving cloud environments.

2. Scalable IoT Data Management: Use the plugin to ingest sensor data from IoT deployments into VictoriaMetrics. This approach facilitates real-time analytics, predictive maintenance, and efficient management of massive volumes of sensor data with minimal storage overhead.

3. Financial Systems Performance Tracking: Leverage VictoriaMetrics via this plugin to store and analyze metrics from financial systems, capturing latency, transaction volume, and error rates. Organizations can rapidly identify and resolve performance bottlenecks, ensuring high availability and regulatory compliance.

4. Cross-Environment Performance Dashboards: Integrate metrics from diverse infrastructure components—such as cloud instances, containers, and physical servers into VictoriaMetrics. Using visualization tools, teams can build comprehensive dashboards for end-to-end performance visibility, proactive troubleshooting, and infrastructure optimization.

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.