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".
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...How can I execute SybaseDebug.bat/SybaseDebug.sh?
This file is used to check if the connectivity and the Discovery of the Sybase Server is possible from the Applications Manager installed server. This standalone program is a excerpt of the same process we use to add the Sybase Server monitor. The ...PHP Monitor Troubleshooting
PHP Monitor Errors and Troubleshooting Guide Check if the phpstats.php file in the webserver's document root. Ensure there are no modifications done in phpstats.php file Check if the given PHP path is correct. Retry with the "SSL is enabled" option ...SNMP Troubleshooting Guide
1) Please check the SNMP agent is running in problematic remote server or not. 2) If it is running then execute the snmpwalk.bat / snmpwalk.sh Note: snmpwalk.bat / snmpwalk.sh troubleshooting script is applicable only for versions v1 and v2. For v3, ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...