Log retention

edit

Log retention

edit

Enterprise Search indexes various event data such as analytics, API requests, and content source events. These event log indexes would grow infinitely in size without retention management. Since 7.9.0, Enterprise Search manages log retention for you, using Index Lifecycle Management (ILM).

Enterprise search creates several ILM policies that manage the Enterprise Search log indexes as they age, automatically transitioning each through a lifecycle. You can find these policies by their IDs to modify them, or you can create your own policies. See:

Enterprise Search uses ILM as long as the underlying Elastic Stack supports the feature. Also, App Search exposes additional controls to disable logging in that product only. See:

Enterprise Search ILM policy IDs

edit

Enterprise Search creates ILM policies with the following IDs:

logs-app_search.analytics-default
logs-app_search.search_relevance_suggestions-default
logs-crawler-default
logs-elastic_crawler-default
logs-enterprise_search.api-default
logs-enterprise_search.audit-default
logs-workplace_search.analytics-default
logs-workplace_search.content_events-default

Manage ILM policies

edit

Manage the above Enterprise Search ILM policies using UIs in Kibana or APIs in Elasticsearch. See:

Disable logging in App Search

edit

Finally, App Search allows admins and developers to disable logging through its log settings UI and API. Although related to log retention, this is a separate feature that is specific to App Search.

See Log settings guide in the App Search documentation.