Description

By default, a healthcheckOSLC command can be used to test services and to determine the health status of a Log Collector in a Log Collector (LC) node. However, the curl commands that are used in Log Collector 17.1 do not work for Log Collector 17.2 and later due to certificate changes.

This article explains how to determine the health status in Log Collector 17.2.

 

Solution

Use the following commands to monitor the health status of the LC node and to check for red indices (damaged or not yet loaded) in the Log Collector.

For Log Collector health status

  • Using the curl command 

[root@LOG-COLLECTOR ~]# curl -k --tlsv1.2 -XGET https://localhost:9200/_cluster/health?pretty=true

{
"cluster_name" : "log-collector",
"status" : "green",                          << LC is in working state
"timed_out" : false,
"number_of_nodes" : 1,
"number_of_data_nodes" : 1,
"active_primary_shards" : 1663,
"active_shards" : 1663,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 0,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 0,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 100.0
}
 

  • Using healthcheckOSLC 

[root@LOG-COLLECTOR ~]# healthcheckOSLC
 

To check for indices in the LC node 

[root@LOG-COLLECTOR ~]# curl -k --tlsv1.2 -XGET https://127.0.0.1:9200/_cat/indices?v
 

To check for red indices in the LC node 

[root@LOG-COLLECTOR ~]# curl -k --tlsv1.2 -XGET https://127.0.0.1:9200/_cat/indices?v | grep –i red