Configuration reference

After editing the configuration, restart the service:

sudo systemctl restart glassmkr-crucible

Configuration is validated at startup. An out-of-range value (for example an interval below the one-minute minimum) is rejected with a message naming the field; see validation behavior for how the agent treats typos and detection-disabling values.

#Full example

A complete file with every option at its default value (except dashboard, shown enabled with a key, which is what init writes). You only need to include the fields you want to change.

server_name: "my-server"

collection:
  interval_seconds: 300
  ipmi: true
  enforce_ipmitool_min_version: false
  smart: true
  thermal: true
  dmi: true

dashboard:
  enabled: true
  url: "https://app.glassmkr.com"
  api_key: "gmk_cru_live_your_key_here"
  tls_pin: ""
  allow_insecure_endpoint: false
  allowed_origins: []

thresholds:
  ram_percent: 90
  swap_alert: true
  disk_percent: 85
  iowait_percent: 20
  nvme_wear_percent: 85
  disk_latency_nvme_ms: 50
  disk_latency_hdd_ms: 200
  cpu_temp_warning_c: 80
  cpu_temp_critical_c: 90
  interface_utilization_percent: 90
  acknowledge_disabled_detection: false

channels:
  telegram:
    enabled: false
    bot_token: ""
    chat_id: ""
  email:
    enabled: false
    to: ""
  slack:
    enabled: false
    webhook_url: ""

prometheus:
  enabled: false
  address: "127.0.0.1"
  port: 9101

#Validation behavior

Three behaviors are worth knowing before you edit:

• Out-of-range values fail at startup with a message naming the field, so a bad edit cannot run silently.
• Unknown keys under collection: produce a startup warning naming the key instead of an error. A typo like enforce_ipmitool_min_versions (plural) would otherwise silently leave the real setting at its default; the warning names the near-miss, and the agent keeps running, because an agent that refuses to start takes monitoring down with it.
• Thresholds pushed to their limits count as disabled detection. A percent threshold at 100, or a latency threshold above 10,000 ms, effectively turns that detection off. The agent warns and flags the snapshot unless you set thresholds.acknowledge_disabled_detection: true to state that this is intentional.

#server_name

#collection

What is collected and how often. Collectors not listed here (RAID, ZFS, GPU, network, security posture, and the rest) run automatically and skip themselves on hosts where their subsystem is absent; they have no config switches.

#dashboard

Connection settings for the Dashboard API, hosted or self-hosted.

#thresholds

Agent-side detection thresholds. Percent thresholds accept 1 to 100. Rule behavior beyond these knobs (severities, evidence, remediation) is documented per rule in the alert rules catalog; rules can also be muted per server from the Dashboard.

#channels

Agent-side notification channels for standalone operation. When the agent reports to a Dashboard, notification routing normally lives there (six channel types, per-priority routing); these agent-side channels exist so a standalone agent can still page someone.

channels.telegram

channels.email

channels.slack

#prometheus

An optional local metrics listener. Off by default: with it off, the agent opens no inbound ports at all.

#Environment variables

The running agent is configured by crucible.yaml only; it does not read configuration overrides from the environment. Two variables exist around the edges of the install flow:

• GLASSMKR_API_KEY: read by the install script as an alternative to passing --api-key (curl -sf https://glassmkr.com/install.sh | sudo GLASSMKR_API_KEY=... bash). The script hands it to glassmkr-crucible init, which writes it into crucible.yaml; the agent then reads the file.
• GLASSMKR_UBUNTU_PRO_TOKEN: optional; read by the agent's CVE collector to query the Ubuntu Pro security feed.

Last verified: 2026-08-29 against the Crucible v1.1.0 config schema (src/config.ts).