You need access to jumphost with you personal Openssh access key (Access an environment via OpenSSH or Putty). In order to use the Elasticsearch API, it is necessary to access the Elasticsearch API from a server from the application network (e.g. web roles). Following API cli commands you may use to identify utilization of your ElasticSearch cluster.
Cluster Health
Information about the health of the entire cluster.
Information about the utilization, roles and master assignments of the individual nodes.
Command (2):
curl -XGET 'https://ENDPOINT/_cat/nodes?v'
host ip heap.percent ram.percent load node.role master name
10.69.57.100 10.69.57.100 76 90 0.04 c - graylog-827fd376-d1b5-49f7-8600-dba8338140ae
10.69.57.143 10.69.57.143 65 95 0.72 d * root360-logmonitoring-es02-i-e240205f
10.69.58.21 10.69.58.21 46 96 0.01 c - graylog-5bd0bac2-d712-4038-a682-089810196c11
10.69.57.70 10.69.57.70 58 96 0.13 d m root360-logmonitoring-es01-i-e4402059
Index Information
Information about status, replication, document count (existing and deleted) and storage size.
Command (3):
curl -XGET 'https://ENDPOINT/_cat/indices?v'
health status index pri rep docs.count docs.deleted store.size pri.store.size
green open index_1 1 1 0 0 260b 130b
green open index_2 1 1 70 3 572.4kb 286.2kb
Storage allocation
Information about Data Nodes and their HDD utilization, as well as Shard number.
curl -XGET 'https://ENDPOINT/_cat/shards?v'
index shard prirep state docs store ip node
graylog_125 1 r STARTED 7473022 4.4gb 10.69.57.70 root360-logmonitoring-es01-i-e4402059
graylog_125 1 p STARTED 7473022 4.4gb 10.69.57.143 root360-logmonitoring-es02-i-e240205f
