We’re pleased to announce Paragon Insights Release 4.2.0. In this section, learn about new and changed features in Paragon Insights Release 4.2.0.
In Paragon Insights Release 4.2.0, you can add multiple return values in user-defined functions. You can configure fields to capture extra return values in the Functions tab on the Rules page. The first return value is stored in the rule field. This feature also helps you reduce the number of UDF files you need to upload in Paragon Automation.
[See Create a New Rule Using Paragon Insights GUI in Paragon Insights Rules and Playbooks.]
Inband Flow Analyzer (IFA) 2.0 is an implementation of Inband Network Telemetry to collect flow data from the forwarding (data) plane and export them to external collectors for analysis. IFA uses probe packets that traverse the same path and queues as packets in the data plane and thus, experience similar latency and congestion. You can use the QFX5120-32C and QFX5120-48Y switches to send IFA 2.0 probe packets that are collected by IFA ingest in Paragon Insights. In Paragon Insights, you must configure nodes in which IFA ingest is deployed and UDP ports in the ingest settings.
[See Understand Inband Telemetry.]
Starting with Paragon Insights Release 4.2.0, you can get a connected view of resources and the dependencies between resources in your network. Resources can be any device components, such as chassis or line card, or network components that span many devices, such as VPN and IPSec. Dependencies between resources show how events in one resource impact other resources, enabling you to analyze root cause of failures triggered by multiple events.
[See Understand Resources and Dependencies.]
Starting in Paragon Insights Release 4.2.0, when you configure a Paragon Insights rule, you can select default sensors that you want to apply to all supported devices, only to Juniper devices, only to Juniper devices that run a specific OS, or to all third-party (non-Juniper) devices.
Starting in Paragon Insights Release 4.2.0, when you commit a configuration, the changes are immediately accepted after validation. A background job that runs periodically tracks these changes and applies the changes to ingest services. Only after the background job applies these changes, does the ingest service process data based on the changes configured. In releases prior to Paragon Insights Release 4.2.0, commit configuration changes are accepted and acknowledged only after the changes are applied to ingest services.
[See Commit or Roll Back Configuration Changes in Paragon Insights.]
Starting with Paragon Insights Release 4.2.0, you can work with Juniper Networks to design default plug-ins. You can also design your own BYOI (custom) plug-in. A BYOI plug-in processes external telemetry data gathered by other collectors and sends the data to the Paragon Insights pipeline for analysis. The BYOI plug-in ingest can import data from different sources such as data lakes that have different data models, different data encoding, and security.
[See Understand Bring Your Own Ingest.]
Python functions called from workflows can have modules that are not supported in default Paragon Insights installation. In such cases, you can include the dependencies necessary for the python functions to work in a bash script and use the script to modify the engine that runs workflows. Starting with Paragon Insights Release 4.2.0, you can run a bash script to modify a workflow in a simulated environment, modify the workflow engine, and rollback the workflow engine to its default state.
[See Modify the UDA, UDF, and Workflow Engines.]
Starting in Paragon Insights Release 4.2.0, you can enable or disable the outbound SSH port for iAgent or the port for native Google Protocol Buffer connections by using the toggle button on the SSH and Native GPB Ingest Settings tabs of the Configuration > Data Ingest > Settings page.
If you enable the Port field, you must specify the port number for SSH or native GPB connections. If you disable the Port field, the port number is cleared.
[See Native GPB and Outbound SSH (Device-Initiated).]
Starting in Paragon Insights Release 4.2.0, you can add vendor identifier, vendor name, default sensors, product, platform, release, and operating system-related information for third-party vendors when you configure rule properties.
Starting in Paragon Insights Release 4.2.0, you can select unsigned integer as a data type when you add a Paragon Insights rule, a raw data summarization profile, or a tagging profile. An unsigned integer data type can contain values from 0 through 4,294,967,295.
In the outlier detection playbook of releases earlier than Paragon Insights Release 4.2.0, you had to provide device IDs of each device in a device group in the XML Path Language (XPath) fields. Starting with Release 4.2.0, you can use the splat operator instead of individual device IDs in the round-trip time (RTT) XPath field of the ICMP outlier detection playbook instances.
[See Create a New Playbook Using the Paragon Insights GUI in Paragon Insights Rules and Playbooks.]
Starting with Paragon Insights 4.2.0, you can view smart alarms on the Alerts page. You can view smart alarms generated by resource dependencies on the Alerts page. Smart alarms is a feature where alarms from different rules are displayed in a tree structure, where the top-level alarm represents the root cause of the other alarm events.
[See Manage Alerts Using Alerts Manager in Alerts and Notifications.]
Starting in Paragon Automation Release 4.2.0, you can apply Paragon Insights filters to view aggregate data of a device group, or view aggregate data of multiple device groups from the Grafana UI. The Juniper Paragon Insights TSDB plug-in that is available with Paragon Insights Release 4.2.0, enables you to apply these filters from the Grafana UI.
[See Grafana Overview.]
Action engine workflow continues to be a Beta feature in Release 4.2.0. Starting in Paragon Insights Release 4.2.0, you can link action engine workflows to rules while setting up triggers. However, you need a PIN-Advanced license for this feature.
Action engine workflow continues to be a beta feature in Release 4.2.0. Starting with Paragon Insights Release 4.2.0, you can add or edit commands, conditions, inputs, and outputs in an action engine workflow from the Configuration > Action Engine page.
[See Manage Action Engine Workflows.]
kube-state-metrics is a beta feature in Paragon Insights Release 4.2.0. kube-state-metrics is a third-party service that generates metrics based on the current state of Kubernetes clusters. kube-state-metrics runs as a cluster service, and is automatically installed when you install Paragon Insights.