Configuration File
The server configuration can be loaded in multiple ways:- Config directory (legacy): Multiple YAML files in a directory structure
- Single config file: Using
--config-fileflag orTEMPORAL_SERVER_CONFIG_FILE_PATHenvironment variable - Embedded config: Default configuration embedded in the binary
Configuration Structure
Top-Level Configuration
Global Configuration
Membership
Cluster membership and gossip protocol configuration.PProf
Go profiling endpoint configuration.TLS Configuration
TLS settings for inter-service and client communication.Server TLS
Client TLS
Metrics
Metrics configuration for Prometheus, StatsD, or M3.Authorization
Authentication and authorization configuration.Persistence Configuration
Database and datastore configuration.Persistence Fields
SQL Datastore
Cassandra Datastore
Elasticsearch Datastore
Service Configuration
Per-service settings for frontend, history, matching, and worker services.RPC Configuration
Dynamic Configuration
Dynamic configuration allows runtime configuration changes without server restart.Archival Configuration
History and visibility archival to long-term storage.Archival States
enabled: Archival is enableddisabled: Archival is disabledpaused: Archival is paused temporarily
Archival Providers
- filestore: Local or network filesystem
- s3store: Amazon S3 or S3-compatible storage
- gstorage: Google Cloud Storage