Status

In the Status tab, it is possible to check the availability of the search service, as well as to view information on the performed indexings: how many records and files have been indexed and the report of the latest indexings.

Search service

The search service displays different colors and messages according to the health of the search engine. See below the possible statuses related to the engine health:

Status	Information
GREEN	Indicates that both Elasticsearch and Atlas are working and there are no index issues. However, it does not necessarily mean that the environment is fully indexed.
RED	Indicates that Atlas cannot connect to Elasticsearch. There may be an Elasticsearch configuration or unavailability issue.
YELLOW	Indicates that there are replicas configured for Elasticsearch, but they are not allocated correctly in their nodes. The Elasticsearch service displays this status when a replica shard is in the same node as the main shard.
CHECK_ERROR	Indicates that SE Suite cannot communicate with the Atlas service. There may be an Atlas configuration or unavailability issue.

In an on-premise environment, with Elasticsearch being managed by the suite (automanaged), it is possible to perform actions such as restarting and configuring the Elasticsearch memory from the Status tab; this option is also valid to reupload the search service if it is not responding.

Indexing

For Elasticsearch to work correctly, its indexes must have been created; with the indexing process, the engine indexes all files within its scope, creating the indexes.

The indexing duration is directly linked to the number of records and files to be indexed, and it may take days in some cases.

Only the txt, doc, docx, xls, xlsx, pdf, eml, odt, ods, ppt, pptx, xml, rtf, and odp extensions can be indexed.