config_opt_missing

Diagnostic `nanook::config::opt_missing`

Summary

required option `{0}` is missing on `{1}`

Help

set {0} in [opts]

Details

When this fires

A registry validator or builder called one of the required-opt methods on Resolver (str, int, float, bool, duration, template) and the key wasn't present in the entry's [opts] table. See crates/nanook-core/src/config/opts.rs. The error names the opt key and the section label (collector / adapter / channel name). You'll see this on nanook check, since that's exactly where static option-shape checks run, and again at nanook run startup.

What to check

The matching docs/content/docs/<collectors|adapters|channels>/<kind>.md page lists every required opt. An option set to "" counts as missing for required fields.

[[collectors]]
name = "api"
kind = "http"
opts = { url = "https://api.example.com/health" }