inputs (Analytics)
Syntax
inputs {
analytics {
parameters {
generate-tags value;
sample-frequency value;
sensors path;
}
}
input-ipfix {
parameters {
maximum-connections number;
tcp-port port-number;
vrf-name name;
}
}
input-jti-ipfix {
parameters {
record-group group-name {
record ipfix-record-name;
reporting-interval seconds;
}
}
}
}
Hierarchy Level
[edit services analytics agent service-agents agent-name]
Description
Configure parameters for a Network Telemetry Framework (NTF) service agent input plug-in. For each service agent instance, you can configure more than one input plug-in to push data to the output plug-in.
When you modify the input plug-in configuration of a service agent instance, the associated service agent daemon is restarted.
Options
| analytics parameters | Configure parameters to collect data from Junos Telemetry Interface (JTI) sensors. |
||||||||||||
| generate-tags value | (Optional) Enable tag generation.
|
||||||||||||
| sample-frequency value | Specify the frequency interval (in seconds) at which the JTI sensor generates data to export to the data collector. Range is from 0 to 24 hours.
|
||||||||||||
| sensors file-path | Specify the resource string associated with the JTI sensor for collecting JTI data from a specific resource. The format is a file path and must be entered exactly. For a list of available JTI resource string options, see the sensor configuration statement and Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface) documentation. |
||||||||||||
| input-ipfix parameters | Configure parameters for the IPFIX mediation service agent to gather and consolidate IPFIX records from downstream devices. Note:
Any change you make to an existing Note:
Although each of the parameters has a default value, you must configure at least one of the parameters to enable the plug-in. If you configure only one parameter and want to use the default value, you must specify that value. |
||||||||||||
| maximum-connections number | (Optional) Maximum number of TCP connections that the IPFIX mediator can support.
|
||||||||||||
| tcp-port port-number | (Optional) TCP port on the IPFIX mediator that receives TCP packets; the listening port.
|
||||||||||||
| vrf-name name | (Optional) Name of the VRF (routing instance) in which IPFIX packets are accepted.
|
||||||||||||
| input-jti-ipfix parameters | Configure parameters for the IPFIX mediation service agent to collect and report local sensor data from the BNG configured as an IPFIX mediator. For each group of records, the plug-in subscribes to the specific sensor data sets associated with each record. When you remove a record group from the configuration, the sensor sets for the member records are unsubscribed. The template IDs for the associated IPFIX records are returned to the pool for re-use. |
||||||||||||
| record ipfix-record-name | One of the following individual IPFIX records associated with a nonconfigurable set of local sensor data. See Telemetry Data Collection on the IPFIX Mediator for Export to an IPFIX Collector for the sensors collected by each record.
Best Practice:
We recommend that you configure the |
||||||||||||
| record-group group-name | Name of a group of IPFIX records that subscribes to the sensor data sets associated with the individual records that comprise the record group. You can configure a maximum of 10 record groups. |
||||||||||||
| reporting-interval seconds | (Optional) Interval in seconds between reports for the subscribed sensor data. The interval applies to all records (and all sensor sets) in the record group.
|
Required Privilege Level
system
Release Information
Statement introduced in Junos OS Release 18.3R1.
input-jti-ipfix option added in Junos OS Release
18.4R1 on MX Series routers.
analytics option added in Junos OS Release 18.4R1
on MX Series and PTX Series routers.