Configuring the Elasticsearch monitor profile
Field | Description |
---|---|
Label | Enter a display name for the monitored cluster. A container will be created with the display name. |
Host Name | Enter the hostname or IP address of any node within the Elasticsearch cluster. For IPv6 address, use the following format: [<IPv6 address>] If the host is present in the AWS environment, you need to add -DES_ENV=AWS in the JVM Arguments field. Note: Square brackets are mandatory for IPv6 address. |
Port Number | Enter the port number of the Elasticsearch service. Default port number is 9200. |
Connection Protocol | Select the connection protocol.
|
Advanced Configuration | |
Read Timeout (seconds) | Enter the timeout period for the HTTP connection. If no data is available at the end of this interval the collector will return an error and proceed with the next scheduled poll. Default value is 50 seconds. |
Maximum Thread Pool Size | This value indicates the maximum number of threads the performance collector can spawn for data collection. In case of large number of indices (more than 1000), this value must be greater than 50. Default value is 50 threads. |
Failover Retry Attempts | Enter the failover retry attempts. This value indicates the number of retries after which collector will activate failover. If a connection node in elasticsearch cluster is down (service is not running) the collector will try to select other nodes from cluster after these attempts are exhausted. Collector will prefer client nodes for connection when failover is initiated. Default value is three retry attempts. |
JVM Arguments | Type the additional Java Virtual Machine arguments for the Java collector. For example, for Java memory settings: -Xms256m -Xmx1024m. Note: If you have AWS-hosted Elasticsearch, enter -DES_ENV=AWS in the field. |
Authentication Details | |
Native/File | |
Username | Enter the username. |
Password | Enter the password. |
PKI | |
Client Certificate File Path (.pfx) | Enter the path (along with the filename and .pfx extension) where the certificate file is located. Note: The client certificate file must reside on the host where the PATROL Agent is running. BMC PATROL default account must have read permission on the directory where the client certificate file is located. The path should be an absolute path to the location where the certificate resides on the PATROL Agent. For example, /home/patrol/membernode.pfx |
Client Certificate Password | Enter a password for the certificate file. |
Index Filter | |
Include Index | Enter the Elasticsearch index name that you want to include for monitoring. Enter a regular expression to include multiple indices. Multiple regular expressions can be given by using pipe as a separator. By default, all indices are included for monitoring. Default value: .* |
Exclude Index | Enter the Elasticsearch index name that you want to exclude from monitoring. Enter a regular expression to exclude multiple indices. Multiple regular expressions can be given by using pipe as a separator. |
Manage Debug | |
Enable PSL Debug | Select this check box to enable the PSL debug. The debug statements are printed to System Output Windows (SOW) or in the issow.log file. The debug file is located at $PATROL_HOME/log/trace/<hostname>/<port>/issow.log |
Java Collector Debug | Select this check box to enable the Java collector debug.
Default log level: WARNING |
Enter the JAVA home details before you save the configuration.
Field | Description |
---|---|
JAVA Home | By default, PATROL for Elasticsearch uses JAVA Runtime Environment (JRE) that is installed with the PATROL Agent. To use your own JRE that is installed in a different location, specify the path for the JAVA home directory. For example, if your JAVA executable exists in the /usr/java/jdk1.8.0_45/jre/bin/java path, specify /usr/java/jdk1.8.0_45/jre as the value in this field. Note: If you have specified a different path in this field, restart the PATROL Agent to apply the changes. |
Enable device mapping | Select/clear this check box to enable/disable device mapping. Enabling device mapping consolidates Elasticsearch monitoring at device level. By default, device mapping is enabled (check box is selected). |