Moldings

Moldings are the individual components that make up a SigNoz deployment. Each molding maps to a service (ClickHouse, PostgreSQL, OTel Collector, etc.) and generates the configuration and deployment files for that service.

Foundry ships with sensible defaults for every molding. Override only what you need by adding a block under spec in your casting.

Components

Key in `spec`	Component	Role
`telemetrykeeper`	ClickHouse Keeper	Cluster coordination for ClickHouse
`telemetrystore`	ClickHouse	Stores logs, traces, and metrics
`metastore`	PostgreSQL or SQLite	Stores metadata (dashboards, alerts, users)
`signoz`	SigNoz	UI and API server
`ingester`	SigNoz OTel Collector	Receives, processes, and writes telemetry data

Processing order

Foundry processes moldings in dependency order during forge:

TelemetryKeeper -> TelemetryStore -> MetaStore -> SigNoz -> Ingester

This ensures each component's configuration can reference its dependencies.

Configuring a molding

Override a molding by giving it a spec block. Whatever you set gets merged with Foundry's defaults.

spec:
  telemetrystore:
    spec:
      image: clickhouse/clickhouse-server:25.5.6
      cluster:
        replicas: 1
        shards: 1

Spec fields

Field	Description
`enabled`	Turn the component on or off (default: `true`)
`image`	Container image (Docker and Kubernetes modes)
`version`	Version label (systemd mode, tagging)
`cluster.replicas`	Number of replicas
`cluster.shards`	Number of shards (TelemetryStore only)
`env`	Environment variables as a key-value map
`config.data`	Config file overrides: filename to file contents

Disabling a molding

Set enabled: false to exclude a component from the deployment:

spec:
  telemetrykeeper:
    spec:
      enabled: false

Custom config files

Use config.data to override the contents of a component's config files. The key is the filename; the value is the file contents.

spec:
  ingester:
    spec:
      config:
        data:
          ingester.yaml: |
            receivers:
              otlp:
                protocols:
                  grpc:
                    endpoint: 0.0.0.0:4317

Note

config.data overrides application-level config files that Foundry understands and manages. For platform-level files (compose files, service units, Kubernetes manifests), use patches instead.

MetaStore kind

The metastore supports two backends. Set the kind field to choose:

spec:
  metastore:
    kind: postgres   # default
    spec:
      image: postgres:16

Kind	Backend	Notes
`postgres`	PostgreSQL	Default. Recommended for production.
`sqlite`	SQLite	Embedded, no external dependency. Single-node only.

Next steps

Casting - the full casting file structure
Annotations - deployment-specific parameters
Patches - platform-level overrides on generated files
Casting file reference - complete field reference

3.1 KiB Raw Permalink Blame History