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.

Note:  The AMX application is pulled once and ingestor details are added. Any new addition can be done by right clicking the AMX app and clicking the Edit option

2. Enter the Alias for the application.
3. In the Ingestor section, enter a port number for the Port.field and select ami or gtpc or gtpc_hier for the Type field.
4. You can export your Application Metadata Intelligence output or control plane metadata to either cloud tools or Kafka. Enter the following details for the Cloud tool export in the Application quick view:

   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 or gtpc for exporting control plane 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 ( _ ).

   

   Enter the following details for Kafka export in the Application quick view:

   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 gtpc 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 secoonds. 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

5. 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.
6. 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.

Note:  If you reload the GigaVUE V Series Node after configuring the AMX application, then the Ingestor in the AMX application fails.

The monitoring session configuration health can be viewed on the Monitoring Session page. Refer Cloud Health Monitoring - Configuration Health Monitoring for more detailed information on how to view cloud configuration health.

To view the application statistics on the Monitoring Session Statistics page, click View Monitoring Session Diagram and click on the AMX application. The Statistics appear as a quick view page. To view the exporter related statistics, select Exporter from the top navigation button on the quick view page.