Configure Application Metadata Exporter Application

To add AMX application:

1. Drag and drop Application Metadata Exporter from APPLICATIONS to the graphical workspace. The Application quick view appears.
2. Enter the Alias for the application.
3. You can export your Application Metadata Intelligence output or control plane metadata to either cloud tools or Kafka. In the Ingestor section, enter or select the following details.

   Fields	Description
   Port	Enter the port number to which the Application Metadata or the Control Plane metadata must be ingested
   Type	Select ami for exporting AMI or mobility_control for exporting control plane metadata.

4. Enter or select the following details in the Metadata Enrichment section:

   Fields	Description
   Enrichment Name	Enter a name for the enrichment.
   Enable	Use this option to enable the enrichment
   Type	Select the type from the drop-down menu.
   Attribute Fields	Select the attributes from the list. You can use the Select All option to select all the available attributes. Refer to Attributes for GigaVUE Enriched Metadata for Mobile Networks section for more detailed information on the list of available attributes and their description.

5. Enter or select the following details in Cloud Tools Export section:

   Fields	Description
   Alias	Enter the alias name for the cloud tool export.
   Cloud Tool	Select the Cloud tool from the drop-down menu.
   Type	Select ami for exporting AMI, mobility_control for exporting control plane metadata, or ami_enriched for exporting enriched metadata
   Account ID	Enter the account ID number of the selected Cloud Tool.
   API Key	Enter the API key of the Cloud Tool.
   Enable Export	Enable the box to export the Application Metadata Intelligence output in JSON format.
   Zip	Enable the box to compress the output file. Note:  Enable this field when using New Relic as the cloud tool.
   Interval	The time interval (in seconds) in which the data should be uploaded periodically. The recommended minimum time interval is 10 seconds and the maximum time interval is 1800 seconds.
   Parallel Writer	Specifies the number of simultaneous JSON exports done.
   Export Retries	The number of times the application tries to export the entries to Cloud Tool. The recommended minimum value is 4 and the maximum is 10.
   Maximum Entries	The number of JSON entries in a file. The maximum number of allowed entries is 5000 and the minimum is 10, however 1000 is the default value.
   Labels	Click Add. Enter the following details: o Enter the Key . o Enter the Value. Note:  When New Relic is selected as the cloud tool, the key is automatically set as is eventType and the Value can only have alphanumeric characters, colons ( : ), periods ( . ), and underscores ( _ ).

6. Enter or select the following details in the Kafka exports section:

   Fields	Description
   Alias	Enter the alias name for the Kafka Export.
   Topic	The topic name to push JSON streams to, which is generally given to users part of the Kafka administration.
   Type	Select ami for exporting AMI or mobility_control for exporting control plane metadata.
   Brokers	The URL that contains the Kafka cluster endpoints. Click to add another broker and click to remove an existing broker.
   Enable Export	Enable the box to export the Application Metadata Intelligence output in JSON format.
   Zip	Enable the box to compress the output file.
   Interval	The time interval (in seconds) in which the data should be uploaded periodically. The recommended minimum time interval is 10 seconds and the maximum time interval is 1800 seconds. The default time interval is 30 seconds.
   Parallel Writer	Specifies the number of simultaneous JSON exports done.
   Export Retries	The number of times the application tries to export the entries to Kafka. The recommended minimum value is 4 and the maximum is 10.
   Maximum Entries	The number of JSON entries in a file. The maximum number of allowed entries is 5000 and the minimum is 10, however 1000 is the default value.
   Labels	Click Add. Enter the following details: o Enter the Key. o Enter the Value.
   Producer Configurations	Click Add to enter the authentication details if a Kafka broker needs authentication. For Example: security.protocol=SASL_SSL sasl.mechanism=PLAIN sasl.username=username sasl.password=password

7. Click Deploy to deploy the monitoring session. The Select nodes to deploy the Monitoring Session dialog box appears. Select the GigaVUE V Series Node for which you wish to deploy the monitoring session.
8. After selecting the V Series Node, select the interfaces for the REPs deployed in the monitoring session from the drop-down menu. Then, click Deploy.

Application Monitoring Options

You can configure the traffic health monitoring for this application in the THRESHOLDS tab. You can select an existing template from the Threshold Templates drop-down menu or provide the threshold values. For more details on Traffic health monitoring and how to create threshold template, refer to Traffic Health Monitoring.

You can view the configuration health status and the traffic health status of the application in the HEALTH STATUS tab. For more details on configuration health and traffic health, refer to Monitor Cloud Health.

You can view the statistics of the application in the STATISTICS tab. Refer to View Application Statistics for Application Metadata Exporter for more detailed information.