JTI OpenConfig Telemetry and Google Cloud Monitoring Integration

Input and output integration overview

<p>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.</p>

<p>The Stackdriver plugin allows users to send metrics directly to a specified project in Google Cloud Monitoring, facilitating robust monitoring capabilities across their cloud resources.</p>

Integration details

JTI OpenConfig Telemetry

<p>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.</p>

Google Cloud Monitoring

<p>This plugin writes metrics to a project in Google Cloud Monitoring, which used to be known as Stackdriver. Authentication is a prerequisite and can be achieved via service accounts or user credentials. The plugin is designed to group metrics by a <code>namespace</code> variable and metric key, facilitating organized data management. However, users are encouraged to use the <code>official</code> naming format for enhanced query efficiency. The plugin supports additional configurations for managing metric representation and allows tags to be treated as resource labels. Notably, it imposes certain restrictions on the data it can accept, such as not allowing string values or points that are out of chronological order.</p>

Configuration

JTI OpenConfig Telemetry

Google Cloud Monitoring

Input and output integration examples

JTI OpenConfig Telemetry

<ol> <li> <p><strong>Network Performance Monitoring</strong>: 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.</p> </li> <li> <p><strong>Automated Fault Detection</strong>: 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.</p> </li> <li> <p><strong>Historical Performance Analysis</strong>: 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.</p> </li> <li> <p><strong>Real-Time Dashboards for Network Operations</strong>: 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.</p> </li> </ol>

Google Cloud Monitoring

<ol> <li> <p><strong>Multi-Project Metric Aggregation</strong>: Use this plugin to send aggregated metrics from various applications across different projects into a single Google Cloud Monitoring project. This use case helps centralize metrics for teams managing multiple applications, providing a unified view for performance monitoring and enhancing decision-making. By configuring different quota projects for billing, organizations can ensure proper cost management while benefiting from a consolidated monitoring strategy.</p> </li> <li> <p><strong>Anomaly Detection Setup</strong>: Integrate the plugin with a machine learning-based analytics tool that identifies anomalies in the collected metrics. Using the historical data provided by the plugin, the tool can learn normal baseline behavior and promptly alert the operations team when unusual patterns arise, enabling proactive troubleshooting and minimizing service disruptions.</p> </li> <li> <p><strong>Dynamic Resource Labeling</strong>: Implement dynamic tagging by utilizing the tags_as_resource_label option to adaptively attach resource labels based on runtime conditions. This setup allows metrics to provide context-sensitive information, such as varying environmental parameters or operational states, enhancing the granularity of monitoring and reporting without changing the fundamental metric structure.</p> </li> <li> <p><strong>Custom Metric Visualization Dashboards</strong>: Leverage the data collected by the Google Cloud Monitoring output plugin to feed a custom metrics visualization dashboard using a third-party framework. By visualizing metrics in real-time, teams can achieve better situational awareness, notably by correlating different metrics, improving operational decision-making, and streamlining performance management workflows.</p> </li> </ol>

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.