ElasticSearch

Introduction

AdmiralCloud uses Elasticsearch as its primary search and indexing backend. All media containers, along with their metadata, channel relations, and security group assignments, are indexed in Elasticsearch to enable fast full-text search and structured filtering via the Search controller.

How indexing works

When you create, update, or delete a media container — or change its metadata, relations, or flags — the change is propagated to Elasticsearch asynchronously. You can monitor this process via the Activity controller: the modelChangesES field reports which documents have been updated in the index and when.

Elasticsearch updates are batched within one-minute windows. This means multiple changes to the same media container within a short period may be combined into a single index update, reducing write load while keeping data consistent.

Checking index state

To determine whether an Elasticsearch update has completed, poll the Activity controller for entries with a matching jobId. Once all activities for a given job are finished (including those with suffixed job IDs like "jobId:1"), the updated data is available in search results.

Custom search configuration

The fields available for search and filtering in Elasticsearch can be configured per customer. Use the GET /v5/misc/configuration/searchConfiguration.mediaContainer endpoint to retrieve the current configuration for your account.