Monitoring

This section lists the key endpoints that system administrators should regularly monitor to ensure SearchBlox and its underlying services are running correctly. Checking these endpoints helps detect service outages, index issues, or configuration problems early before they impact end users.

Critical Monitoring Endpoints

The following endpoints are the most important ones to monitor. Each one covers a different part of the SearchBlox system — the admin interface, the search interface, and the OpenSearch engine. Regularly verifying these endpoints ensures all core components are healthy and accessible.

1. Admin Access Endpoint:

URL: https://<domain>:<port>/console
(Default: https://localhost:8443/console)
Expected Response: HTTP 200 OK
Troubleshooting:
If inaccessible, verify SearchBlox service status
Restart service if necessary:

systemctl restart searchblox

2. Search Access Endpoint:

URL: https://<domain>:<port>/search/index.html
(Default: https://localhost:8443/search/index.html)
Expected Response: HTTP 200 OK
Troubleshooting:
Check service logs for errors
Verify port configuration if connection fails

3. Opensearch Access Endpoint:

URL: https://\<IP_Address>:9200/\_cat/indices?v
(Default: https://localhost:9200/_cat/indices?v)
Expected Response: HTTP 200 OK with index listing

If Opensearch service is accessible, please check the status of indexes.

Status Indicator	Status Indicator	Recommended Action
Red status	Index is corrupted/unavailable	1. Restart SearchBlox 2. If unresolved, delete and recreate index
Closed status	Index exists but is inactive	1. Attempt to open index 2. Restart service 3. Delete if unrecoverable
Yellow status	Partial availability (expected during maintenance)	Monitor for automatic recovery
Green status	Healthy and fully functional	No action required

Please refer the following links:
status-of-indices-red-or-closed
deleting-opensearch-indices