Elasticsearch service is not discovered with VMware Application Proxy

Products

• VMware
• VMware Aria Suite

Issue/Introduction

Symptoms:

• VMware Application Proxy fails to discover the Elasticsearch service.

Environment

VMware Application Proxy 1.x
VMware vRealize Operations Manager 6.7.x

Cause

VMware Application Proxy is looking for a specific instance name of Elasticsearch.
Depending on the installation of Elasticsearch, the service name can be created with slightly different names, such as elasticsearch.

Resolution

This is a known issue affecting VMware Application Proxy.

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

Workaround:
To resolve this issue, edit the discovery content name for elasticsearch.

1. Log into the VMware Application Proxy VM as root via SSH or console.
2. Open /ucp/ucp-config-scripts/service-discovery/sd-svc-signatures-windows.yaml in a text editor.
3. Search for the elasticsearch service signature and edit the name_regex entry to be '^.*[Ee]lasticsearch.*'.

Example:
    elasticsearch:
        bin_name: 'elasticsearch%'
        name_regex: '^.*[Ee]lasticsearch.*'
        display_name: Elasticsearch
        vendor: Elasticsearch BV

4. Save and close the file.
5. Reload the configuration files by running this command:

/ucp/ucp-config-scripts/ucp-firstboot.sh

6. Uninstall, then reinstall the VMware Application Proxy agent on any machines utilizing elasticsearch.