Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Understand Bring Your Own Ingest

Paragon Automation offers default Bring Your Own Ingest (BYOI) plug-ins and support for custom BYOI plug-ins. BYOI plug-ins ingest telemetry data that is stored in third-party sources such as a data lake or external databases. You can export such telemetry data, collected using your infrastructure, through the BYOI plug-in and store it in the Paragon Automation time series database (TSDB).

Bring Your Own Ingest Plugins include an input plugin that is developed by the user and the output plugin developed for Paragon Automation by Juniper Networks. The BYOI input plugin streams data from different data sources (Kafka) that use different data models (OpenConfig or NETCONF YANG), data encoding (Extended Markup Language or JavaScript Object Notation-based), data security, and messaging buses (Kafka), and sends the data to the output plugin. The output plugin converts data into the line protocol format and writes the data to the Paragon Automation TSDB.

Paragon Automation supports two types of plugins:

  • Default Plugin—You can use default plugins to measure metrics that are unique to your network. You can work with Juniper Networks to develop default BYOI plug-ins.

    To load a default plug-in, you require Paragon Automation Release 21.3 or later. After you load the default plug-in, it is listed in the Default Plugins tab of the BYOI Plugins page. All default plug-ins must be mapped to existing or new device groups. Ensure that you deploy playbook instances on the device groups mapped to the plug-in ingest.

    Juniper Network develops and sends you the default plug-ins, with the Kubernetes YAML files and the plugin configurations that are included as a compressed tar file.

  • Custom Plugin—You can use custom plug-in when you want to stream pre-existing telemetry data to Paragon Automation for analysis. You must develop the BYOI plug-in, build the BYOI plug-in ingest image, and load the plug-in image and Kubernetes YAML file for the plug-in to the Paragon Automation server.

    To load a custom plug-in, you require Paragon Automation Release 22.1 or later. After you successfully load the custom plug-in, it is listed in the Custom Plugins tab of the Bring Your Own Ingest Plugin page.

    Custom plug-ins do not support the default rules, playbooks, and device groups in Paragon Automation. Therefore, you should write your own rules and playbooks and add a device group for the custom ingest plugin.


Deploying bring your own ingest plug-ins has the following benefits:

  • Reduces the cost of collecting telemetry data from devices by reusing already collected data to Paragon Automation.
  • You can use all Paragon Automation features—such as custom or default rules, playbooks, reports, graphs, network health view, and more—on the external data you ingest into Paragon Automation.