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. To learn how to configure the proxy, [click here].
-
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.
-
Details of the 'Master node' or 'Data node' of the Elasticsearch cluster should be provided to add all the sub nodes in the cluster, since only they contain the details of 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 ...Troubleshooting Failed Diagnostic Tests
This KB is intended for troubleshooting Diagnostic Tests with Failed results. If you encounter any errors displayed in the monitor that prevent the execution of Diagnostic tests, or if there is no data available for Diagnostic Tests, please refer ...APM Insight - Agents Troubleshooting and Compatibility Guide
To optimize performance and troubleshooting, Please provide the following details related to the respective agents and cross-verify compatibility from the provided help pages. Java Agent Application Server & Version : __________________ [Eg. Apache ...SAP HANA Troubleshooting
Problem 1: No Data in SAP HANA Database monitor (or) "SAP DBTech JDBC: [414]: As per your password policy,current user is forced to change DB password." error message is shown. Solution: Change SAP HANA DB password or Update Password policy. Refer ...Troubleshooting Server error responses
Server error responses Internal Server Error, Bad Gateway, Service Unavailable and Gateway Timeout are the most common server error messages. Seeing any one among these errors generally indicates an issue with the URL's server. Troubleshooting for ...