Determining your current shard consumption

Connect to Elasticsearch

1. Log in to your Red Hat® OpenShift® cluster, or SSH into a control plane node or the loadbalancer VM on your Linux® deployment. Then swtich to the namespace where IBM Cloud Pak for AIOps is installed.

   oc project <project>
   

   Where <project> is the project that your IBM Cloud Pak for AIOps installation is deployed in.

2. Run the following command to list the indices stored in Elasticsearch. Look for index files that have a 1000-1000-<date>-logtrain name format, such as 1000-1000-20210510-logtrain.

   export ELASTIC_SET="$(oc get statefulset -l app.kubernetes.io/managed-by=ibm-elasticsearch -o jsonpath='{.items[0].metadata.name}')"
   oc exec "statefulset/${ELASTIC_SET}" -- curl -XGET -k --fail "http://127.0.0.1:19200/_cat/indices?v" | sort
   

   Example output, where the index name is 1000-1000-20220302-logtrain:

   green open 1000-1000-20220302-logtrain        eEvaBufQ06yG074hmeHKG  8 1 244 6 72.7kb 72.7kb 
   

   The following table lists the elements in this line of output:

   Table. elements

   Element	Description	Example
   Index health	Health of the index.	green
   Index Status	Status of the index.	open
   Index name	Name of the index.	1000-1000-20220302-logtrain
   UUID	Universal unique identifier for this index.	eEvaBufQ06yG074hmeHKG
   Number of shards	Number of shards required by default for this index. This value varies based on the type of index. For example, an index that is associated with a day of ingested log data for natural language log anomaly training requires 8 shards for both a large and a small installation.	8
   Number of replicas	Number of replicas required by default for this index. This value varies based on the type of index and the size of the installation. For example, an index that is associated with a day of ingested log data for natural language log anomaly training requires 1 replica for a large installation and 0 replicas for a small installation. A replica value of 1 replicates all of the shards for that index, meaning that a shard replica setting of 8/1 assigns 16 shards to the index.	1
   docs.count	Detailed statistic associated with this index.	244
   docs.deleted	Detailed statistic associated with this index.	6
   Store size	Detailed statistic associated with this index.	72.7 kb
   Primary store size	Detailed statistic associated with this index.	72.7 kb

3. Check the count of the records for an index by using the following command:

   export INDEX_NAME=<index name>
   export ELASTIC_SET="$(oc get statefulset -l app.kubernetes.io/managed-by=ibm-elasticsearch -o jsonpath='{.items[0].metadata.name}')"
   oc exec "statefulset/${ELASTIC_SET}" -- curl -XGET -k --fail "http://127.0.0.1:19200/${INDEX_NAME}/_count"
   

   Where <index_name> is the name of an index returned by the previous step

   Example output:

   {"count":318713,"_shards":{"total":1,"successful":1,"skipped":0,"failed":0}}
   

4. You can also look at sample data by using the following command:

   export INDEX_NAME=<index name>
   export ELASTIC_SET="$(oc get statefulset -l app.kubernetes.io/managed-by=ibm-elasticsearch -o jsonpath='{.items[0].metadata.name}')"
   oc exec "statefulset/${ELASTIC_SET}" -- curl -XGET -k --fail "http://127.0.0.1:19200/${INDEX_NAME}/_search"
   

   Where <index_name> is the name of an index returned by the previous step.