Troubleshooting - Elasticsearch
To troubleshoot Elastic Search Monitor, follow the below steps:
- Verify Accessibility: Ensure that the Elastic search instance is accessible from the Applications Manager server.
-
Check Host and Port: Make sure you’ve entered the correct host and port number for your Elastic search server.
-
SSL Configuration: Retry adding the monitor with the "SSL is enabled" option both enabled and disabled.
-
Test Elastic search API Accessibility: Verify that the Elastic search API (http(s)://[HOST]:[PORT]/_cluster/health) is accessible from the Applications Manager server.
-
Proxy Server Configuration: If your environment requires the use of a proxy server to access the Elastic search API, configure the proxy in Applications Manager. Click here to learn how to configure the proxy.
-
Bypass Proxy for Elastic search: If you have configured a proxy in Applications Manager but want to bypass it for the Elastic search server host/IP, add the host/IP under the "Do not use proxy for addresses beginning with" section in the "Configure Proxy" page: Navigate to Settings > Product Settings > Proxy Server Settings.
-
To add all sub-nodes in the Elasticsearch cluster, you need to provide details of the 'Master node' or 'Data node', as they hold information about all the nodes in the cluster.
Still facing issues?
If the problem persists, contact our support team along with the following details:
- A screenshot of the "Add Monitor" page.
- The URL debug tool response for the Elastic search monitor.
- Reproduce the issue and share the latest Support Information File (SIF) from Applications Manager, with the "Print all logs" option enabled. To do this, go to Settings > Logging, and choose "Print all logs".