OpenSearch installation

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

After installing or configuring OpenSearch/ElastiSearch in a VMware Smart Assurance (Smarts) environment, the OpenSearch service does not appear as "attached" to the broker when running the brcontrol command. Users may mistakenly assume the service is not running or has failed to integrate with the Smarts broker.

Environment

All supported Smart releases

Cause

This behavior is expected by design. EDAA services—specifically Tomcat, RabbitMQ, and OpenSearch/ElasticSearch—are not Smarts domain managers. Because they do not function as domain managers, they are not registered in the same manner as traditional Smarts components and will not be displayed in the standard brcontrol output.

Resolution

To verify the status of OpenSearch and other EDAA services, do not rely on brcontrol. Instead, use the following methods:

1. Check Service Status Directly: Use operating system-level commands (e.g., sm_service show) to verify that the OpenSearch process is active and running.
2. Review Logs: Inspect the OpenSearch and EDAA-specific logs for any initialization errors or connectivity issues.