Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Supported Platforms

 

Related Documentation

 

export-profiles

Syntax

export-profiles {profile-name {interface {information;statistics {queue;traffic;}status {link;queue;traffic;}}stream-format format;system {information;status {queue;traffic;}}}}

Hierarchy Level

[edit services analytics]

Release Information

Statement introduced in Junos OS Release 13.2 for the QFX Series.

Description

Configure an profile to specify the network analytics data being streamed to remote servers. Each profile is a template that defines the type of data being streamed.

Note: The export-profile statement is available in Junos OS Release 13.2X51-D15 or later.

Options

profile-name

Name of the export profile containing the configuration of the data being streamed.

stream-format format

Format of the streaming data being sent to a server. Only one format can be sent to each port on a server.

Values:

  • csv—Comma-separated Values (CSV). Data sent in this format is newline separated, and each record contains one stream type (queue or traffic data) per interface.Each record contains either a “q” for a queue statistics, or a “t” for a traffic statistics.
  • gpb—Google Protocol Buffer (GPB). Data sent in this format has a hierachical format, and is categorized by resource type (system or interfaces), which is specified in the message header. You can generate data formatted in other formats (CSV, TSV, and JSON) from GPB-encoded data.

    Each message includes a 8-byte header containing the following information:

    • Bytes 0 to 3—Length of the message.
    • Byte 4—Message version.
    • Bytes 5 to 7—Reserved for future use.

    Note: A schema file called analytics.proto containing the definitions of the GPB messages is available for downloading from the following location:

    https://www.juniper.net/techpubs/en_US/junos13.2/topics/reference/proto-files/analytics-proto.txt

  • json—JavaScript Object Notation (JSON). Data sent in this format is newline separated, and each record contains one stream type (queue or traffic data) per interface. Each record contains either “queue-statistics” or “traffic-statistics” in the “record type” field.
  • tsv—Tab-separated Values (TSV). Data sent in this format is newline separated, and each record contains one stream type (queue or traffic data) per interface. Each record contains a “q” for a queue statistics, or a “t” for a traffic statistics.

The remaining statements are explained separately.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

 

Related Documentation

 

Published: 2014-07-23

Supported Platforms

 

Related Documentation

 

Published: 2014-07-23