Elastic Search indices introduction and management

Index	Description
statistics:	This index is used for showing information in Elastic Search Homepage widgets. Since 2021-06, purging of statistics is available in ION Desk > Purge Data. For older versions, the manual process must be used as described in KB 2094746: In the Grid, stop the OneView node (by setting the binding to 0) or stop the entire Grid. Using Postman to call `DELETE http://<hostname>:9200/statistics/`. In the Grid, start the OneView node (by setting the binding to 1) or start the entire Grid. The Statistics index can grow rapidly and is typically the largest index, but this is fully related to the volume of events, workflows, tasks, alerts, and so on. Ensure to provide enough disk space.
event:	This index is used for showing BODs in OneView. BOD purging is required to limit the size.
message:	This index is used for showing BODs in OneView. BOD purging is required to limit the size.
mes$monitor:*	These indices are used for widget data metrics as an insight into the Elasticsearch cluster. These are numerous, but they will remain very low in size.
ionapimetadata_infor:	This index is used for the metadata. It consumes space in proportion to how many API endpoints are defined and is typically small at customers.
gateway_tracing_infor:	This index is used for ION API Gateway when tracing is enabled (default). There is NO automated purging process in On-Premises versions, but it can be automated as described in KB 2068231, using the tracingHelper from the IONGateway directory to delete data older than 31 days. If fewer days should be stored, edit the `bin\tracingHelper.js` at line 38 and change the value 31 to a smaller number such as 10. Tracing can be enabled or disabled via ION API > Monitoring. The ION API Monitoring tile shows the status. Clicking the tile allows to enable or disable tracing per endpoint.
ionapigateway:	This index was used for statistics data shown in certain widgets. As of version 12.0.35 it is no longer used, and the widgets get their data from the gateway_tracing_infor index. After upgrade to 12.0.35 or higher versions, the ionapigateway index can safely be removed by manually deleting it via Postman.
mes$i$v2$lid_infor.social.1$mingle_:*	These are created for Infor Ming.le Portal data like users, groups, alerts, posts, stream, tasks, and templates. The size will be small typically.
mes$i$v2$lid_infor.daf.1$ <DocumentName>{}:{*}	These are created for each document type in IDM having Text searchable enabled, and dropped again when this is disabled. The size will depend on number of documents and size.

statistics:

This index is used for showing information in Elastic Search Homepage widgets. Since 2021-06, purging of statistics is available in ION Desk > Purge Data.

For older versions, the manual process must be used as described in KB 2094746: In the Grid, stop the OneView node (by setting the binding to 0) or stop the entire Grid. Using Postman to call DELETE http://<hostname>:9200/statistics/. In the Grid, start the OneView node (by setting the binding to 1) or start the entire Grid.

The Statistics index can grow rapidly and is typically the largest index, but this is fully related to the volume of events, workflows, tasks, alerts, and so on. Ensure to provide enough disk space.

event:

This index is used for showing BODs in OneView. BOD purging is required to limit the size.

message:

This index is used for showing BODs in OneView. BOD purging is required to limit the size.

mes$monitor:*

These indices are used for widget data metrics as an insight into the Elasticsearch cluster. These are numerous, but they will remain very low in size.

ionapimetadata_infor:

This index is used for the metadata. It consumes space in proportion to how many API endpoints are defined and is typically small at customers.

gateway_tracing_infor:

This index is used for ION API Gateway when tracing is enabled (default). There is NO automated purging process in On-Premises versions, but it can be automated as described in KB 2068231, using the tracingHelper from the IONGateway directory to delete data older than 31 days. If fewer days should be stored, edit the bin\tracingHelper.js at line 38 and change the value 31 to a smaller number such as 10.

Tracing can be enabled or disabled via ION API > Monitoring. The ION API Monitoring tile shows the status. Clicking the tile allows to enable or disable tracing per endpoint.

ionapigateway:

This index was used for statistics data shown in certain widgets. As of version 12.0.35 it is no longer used, and the widgets get their data from the gateway_tracing_infor index. After upgrade to 12.0.35 or higher versions, the ionapigateway index can safely be removed by manually deleting it via Postman.

mes$i$v2$lid_infor.social.1$mingle_:*

These are created for Infor Ming.le Portal data like users, groups, alerts, posts, stream, tasks, and templates. The size will be small typically.

mes$i$v2$lid_infor.daf.1$ <DocumentName>{}:{*}

These are created for each document type in IDM having Text searchable enabled, and dropped again when this is disabled. The size will depend on number of documents and size.