Architecture

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.
CloudPrem is in Preview.

Overview

CloudPrem architecture showing Indexers, Searchers, Metastore, and Control Plane components interacting with object storage

CloudPrem uses a decoupled architecture which separates the compute (indexing and searching) and data on an object storage. This allows for independent scaling and optimization of different cluster components based on workload demands.

Components

The CloudPrem cluster, typically deployed on Kubernetes (EKS), consists of several components:

Indexers
Responsible for receiving logs from Datadog Agents. Indexers process, index, and store logs in index files called splits to the object storage (for example, Amazon S3).
Searchers
Handle search queries from the Datadog UI, reading metadata from Metastore and fetching data from the object storage.
Metastore
Stores metadata about the indexes, including split locations on the object storage. CloudPrem uses PostgreSQL for this purpose.
Control Plane
Schedules indexing jobs called indexing pipelines on indexers.
Janitor
Performs maintenance tasks, applying retention policies, garbage collecting expired splits, and running delete query jobs.

Further reading

PREVIEWING: esther/docs-10024-cloud-prem