We’re pleased to announce Paragon Insights Release 4.0.0. In this section learn about new and changed features in Paragon Insights Release 4.0.0.
Support for Dynamic Tagging—Paragon Insights Release 4.0.0 supports dynamic tagging. In dynamic tagging, you can set conditions in a tagging profile that, in turn, are checked against values stored in the Redis database. When these conditions are met, they are applied to incoming data before Paragon Insights processes the data. The Redis database acts like a cache memory that stores real-time data. In earlier releases, Paragon Insights supports static tagging where conditions are checked against values stored in the times series database (TSDB). Values stored in TSDB are constants and rarely change.
[See Paragon Insights Tagging.]
Support for Paragon Insights Ingest Scale-out Based on Number of Devices—Starting in Paragon Insights Release 4.0.0, you can add more than 50 devices per device group. However, the actual scale of the number of devices you can add depends on the available system resources.
For example, consider that you want to create a device group of 120 devices. In releases before Release 4.0.0, we recommend that you create three device groups of 50, 50, and 20 devices, respectively. With Paragon Insights Release 4.0.0, you just create one device group.
Support for Data Rollup Summarization—Starting in Paragon Insights Release 4.0.0, you can summarize field data by creating a data rollup summarization profile. Field data is processed data that provides information about a network device and its components, and is stored in the time series database (TSBD).
[See Configure Data Summarization.]
Support for Configuring Header Pattern of Unstructured Syslog Message—Starting in Paragon Insights Release 4.0.0, you can configure the pattern for parsing the header portion of a syslog message. In this release, we support parsing of unstructured syslog messages of non-Juniper devices. In earlier releases, you can parse only the payload portion of either a structured syslog message (as specified in RFC 5424), or a Juniper device’s unstructured syslog message.
Support to Configure Multiple Sensors Per Rule in a Device—Starting with Paragon Insights Release 4.0.0, an sp-admin user can add multiple sensors per rule that can be applied to a device group. Data from multiple sensors are populated in a single TSDB field table that can be easily exported or used for visualization.
[See the Multiple Sensors per Device section in Paragon Insights Concepts.]
Support to Configure Sensor Precedence in Rule Properties—Starting with Paragon Insights Release 4.0.0, sp-admin users can configure sensor precedence in the MGD CLI. This allows you to apply multiple sensors in a rule to a device group comprising multivendor devices with differences in operating system, release versions, and so on.
[See the Sensor Precedence section in Paragon Insights Concepts.]
Support for IAM-Based Services—Starting with Release 4.0.0, Paragon Insights executes user management, authentication, and authorization through the Identity and Access Management (IAM) service available in the 4.0.0 installation package. The IAM service effects the following changes:
The hbadmin, hbconfig, hbmonitor, and hboperator groups are migrated to sp-admin and sp-operator roles.
The sp-admin can also back up and restore both deployed and undeployed configuration settings of resources in Paragon Insights. The backup does not include pre-canned roles in the interface.
System administrators can reset password of the default admin user in standalone Paragon Insights deployments. System administrators must run a CURL command in a shell of any node in the Kubernetes cluster that hosts Paragon Insights.
LDAP users can access the Paragon Insights GUI after configuring LDAP settings in Paragon Insights and mapping LDAP user groups to Paragon Insights roles.
For more information about first login, user management, and password recovery, see Manage Paragon Insights Users and Groups.
Support for SNMPv3 and SNMPv2c Ingests—Starting with Paragon Insight Release 4.0.0, users with the sp-admin role can configure SNMPv3 and SNMPv2c ingest methods in the Paragon Insights GUI at the device and device group level. SNMPv3 offers an option to authenticate and encrypt messages between Paragon Insights and the network elements such as devices or device group.
Support for SNMP Trap and Inform Notifications—Starting with Paragon Insights Release 4.0.0, an sp-admin can configure devices to send trap notifications to Paragon Insights using SNMPv3 and SNMPv2c. You can also configure SNMPv3 inform notifications at the device level or the ingest level in Paragon Insights.
Support for TSDB Dashlets and GUI Enhancements in Paragon Insights—Starting with Release 4.0.0, you can use the following enhancements in the Paragon Insights GUI:
Favorites option—You can bookmark pages under the Favorites section for easier access.
Launchpad menu (rocket icon)—In the top right corner of the UI, if you click the Launchpad button (rocket icon), you get a drop-down menu that takes you to the Sizing Tool and the Github repository for Paragon Insights rules called Playbooks (github).
TSDB dashlets in dashboard—Consists of TSDB dashlets that have line charts for Buffered Bytes, and Buffer Length, and donut charts for Read Error for Last 5 Minutes, Write Error for Last 5 Minutes, and Buffer Length
Alerts—We’ve renamed the alarm section accessible from the Monitor menu in the left navigation bar in the GUI as Alerts. To access the Alerts page, go to Monitor > Alerts.
User login session—A login session expires in 30 minutes. After 25 minutes, the Session Expiration page is displayed. To extend the session, select No. If you select Yes, you will be logged out immediately.
Note This restriction is not applicable if your role is noc-operator.
[See Monitor Device and Network Health.]
Support for Arista Networks, Linux, and Palo Alto Networks Devices—Starting with Paragon Insights Release 4.0.0, you can add devices belonging to Arista Networks, Linux, and Palo Alto Networks when you configure a new device.
[See the Adding a Device section of the Manage Devices, Device Groups, and Network Groups topic.]
Support for EOS, PAN-OS, and NX-OS Operating Systems—Starting with Paragon Insights Release 4.0.0, you can add EOS, PAN-OS, and NX-OS operating systems when you configure a new device.
For more information, see the Adding a Device section of the Manage Devices, Device Groups, and Network Groups topic.
Support for Cloning NetFlow Template, Syslog Pattern, and Syslog Pattern Set—Starting with Paragon Insights Release 4.0.0, you can clone an existing NetFlow template, syslog pattern, and syslog pattern set.
For more information, see Paragon Insights Push-Model Ingest Methods.
Support for AMQP Publish—Starting with Paragon Insights Release 4.0.0, you can set the notification type as AMQP Publish on the Settings > System > Add Notification (+) page. You can use AMQP Publish to stream sensor data, field data, and alert notifications to Advanced Message Queuing Protocol (AMQP).
[See Alarms and Notifications.]
Support for RHEL 8 and CentOS 8—Starting with Paragon Insights Release 4.0.0, for an online installation of Paragon Insights, we support::
Red Hat Enterprise Linux (RHEL) version 7, Release 7.5 or later; RHEL version 8, Release 8.2 or later.
CentOS version 7, Release 7.3 or later; CentOS version 8, Release 8.2 or later.
Starting with Paragon Insights Release 4.0.0, for an offline installation of Paragon Insights, we support:
RHEL version 7, Release 7.5 or later; RHEL version 8, Release 8.3 or later.
CentOS version 7, Release 7.3 or later; CentOS version 8, Release 8.3 or later.
No Kernel Upgrade for Multinode Installation—Paragon Insights Release 4.0.0 supports RHEL version 8 and CentOS version 8. With this support, you don’t require kernel upgrade for single-node and multinode installation.
Support for Multi-master Nodes—Starting with Paragon Insights Release 4.0.0, while installing Paragon Insights you can choose to have multiple master nodes.
While running the healthbot setup command, you are prompted to specify hostnames or IP addresses of the master nodes. If you choose to have multiple master nodes, you must also specify the virtual IP address that is required for configuring high availability (HA) between the master nodes. If you are using the silent installer, in the configuration file you can specify the virtual IP address in the master_virtual_ip field.
For more information, see Paragon Insights Installation Requirements.
Multi-NIC Support—Starting with Paragon Insights Release 4.0.0, while installing Paragon Insights you can specify multiple virtual IP (VIP) addresses (unused) so that you can connect to various services in Paragon Insights. You can thereby monitor devices that are in different subnets. If you are using the silent installer, in the configuration file you can specify multiple VIP addresses in the load_balancer_ip field.