Understand Bring Your Own Ingest

Paragon Automation provides Bring Your Own Ingest (BYOI) default plug-ins and support for BYOI custom 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 that you collected through the BYOI plug-ins and store it in the Paragon Automation time series database (TSDB).

You can develop BYOI custom plug-ins to ingest data from different sources, and send data in the line protocol format to the terminus pod. The terminus pod is the entry point to the rest of the Paragon Automation (Insights) pipeline. BYOI custom plug-ins can be written in any programming language, however, a performant programming language (C, C++, Golang etc.) is preferred.

When a playbook is deployed on a device group with rules associated to BYOI custom plug-ins, the ingest and terminus pods are created. The ingest image forwards ingest data to the backend terminus pod by using the Kubernetes service.

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. 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. For more information on the workflow to deploy a default plug-in Bring Your Own Ingest Default Plug-in Workflow.
• 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.