Prerequisites for Application Metadata Exporter

Prerequisites for AWS

Prerequisites to follow when creating a monitoring domain and deploying a V Series node in AWS:

  • Select Traffic Acquisition Method as Customer Orchestrated Source. For details, refer to Create a Monitoring Domain.
  • Select Instance type with three or more NICs. For details on deploying a GigaVUE V Series Node, refer to Configure GigaVUE Fabric Components in GigaVUE-FM.
  • When the Traffic Acquisition Method is selected as Customer Orchestrated Source, the Volume Size field appears on the AWS Fabric Launch Configuration page. Enter the Volume Size as 80GB.

    Note:  Purge begins automatically when the disk space reaches 50%.

Prerequisites for Azure

Prerequisites to follow when creating a monitoring domain and deploying V Series node in Azure:

  • Select Traffic Acquisition Method as Customer Orchestrated Source. For details, refer to Create Monitoring Domain.
  • Select Size with three or more NICs. For details on deploying a GigaVUE V Series Node, refer to Configure GigaVUE Fabric Components in GigaVUE‑FM.
  • When the Traffic Acquisition Method is selected as Customer Orchestrated Source, the Disk Size field appears on the Azure Fabric Launch Configuration page. Enter the Disk Size as 80GB.

    Note:  Purge begins automatically when the disk space reaches 50%.

Prerequisites for VMware

Prerequisites to follow when creating a monitoring domain and deploying V Series node in VMware:

  • Select Traffic Acquisition Method as Customer Orchestrated Source. For details, refer to Create Monitoring Domain for VMware ESXi..
  • .When deploying this application in VMware NSX-T, create a monitoring domain in the ESXi Monitoring domain. Even if your GigaVUE V Series Node is a part of VMware NSX-T host, you can still deploy it in VMware ESXi monitoring domain. For details, refer to the Same Host across Different Monitoring Domains topic in the GigaVUE Cloud Suite Deployment Guide - VMware.