VMware Edge Intelligence is a vendor agnostic AIOps solution focused on the enterprise Edge that ensures end-user and Internet of Things (IoT) client performance, security, and self-healing through wireless and wired LAN, SD-WAN, and Secure Access Service Edge (SASE). Integration of VMware Edge Intelligence with VMware helps extend visibility from SD-WAN to branch, campus, and home. This integration helps VMware Edge Intelligence to get data from different vantage points for each application flow, which includes wireless controller, LAN switch, network services, VMware SD-WAN Edge, VMware SD-WAN Hub, VMware SD-WAN Gateway, and application performance metrics. For more information, see VMware Edge Intelligence Configuration Guide.

VMware provides pre-defined system properties to configure VMware Edge Intelligence feature in the SASE Orchestrator portal. An Operator Super user can add or modify the values of the system properties to activate the Analytics service in a SASE Orchestrator.

The following table describes all the VMware Edge Intelligence-related system properties. When enabling EI for a SASE Orchestrator, ensure that the following system properties are properly set in the SASE Orchestrator.

System Property Description Value
session.options.enableEdgeAnalytics Activate the Analytics service on a SASE Orchestrator. By default, Analytics is activated for Cloud-hosted Orchestrators.
Note: For On-prem Orchestrators, this system property is set to false by default. Ensure to change the value to true if you want to activate the Edge Intelligence feature.
true
service.analytics.apiURL URL of the Analytics API https://integration.nyansa.com/vco/api/v0/graphql
service.analytics.apiToken API token of the Analytics API. The SASE Orchestrator uses the API URL and token to contact the Cloud Analytics Engine and create new customers/SD-WAN Edges in the Analytics Engine. For hosted Orchestrators, VMware Edge Ops can generate this token. And for on-prem Orchestrators, the Operator users should contact their SE or AE and ask them to email the EI-Activations DL to request the service.analytics.apiToken. For information on how to contact the Support Provider, see https://knowledge.broadcom.com/external/article?legacyId=53907.
service.analytics.configEndpoint Configuration endpoint of Analytics service
  • config.nyansa.com (dynamic) or config-m2.nyansa.com (static) - For Orchestrators located in any region except for EMEA to connect to the US EI instance.
  • config.eu.nyansa.com (dynamic) or config-m2.eu.nyansa.com (static) - For Orchestrators located in the EMEA region to connect to the EMEA EI instance.
  • config.ap.nyansa.com (dynamic) or config-m2.ap.nyansa.com (static) - For Orchestrators located in the APAC region to connect to the Sydney EI instance.
service.analytics.analyticsEndpointStatic IP analytics endpoint of Analytics service
  • loupe-m.nyansa.com (dynamic) or loupe-m2.nyansa.com (static) - For Orchestrators located in any region except for EMEA to connect to the US EI instance.
  • loupe-m.eu.nyansa.com (dynamic) or loupe-m2.eu.nyansa.com (static) - For Orchestrators located in the EMEA region to connect to the EMEA EI instance.
  • loupe-m.ap.nyansa.com (dynamic) or loupe-m2.ap.nyansa.com (static) - For Orchestrators located in the APAC region to connect to the Sydney EI instance.
service.analytics.analyticsEndpointDynamic IP analytics endpoint of Analytics service Same values as service.analytics.analyticsEndpointStatic.