Declarative Configuration Conventions

Why declarative config is the default for new projects

Prefer declarative YAML configuration over scattered OTEL_* environment variables and over programmatic SDK construction:

• It's language-agnostic (same YAML works across Go, Java, JS, etc.)
• It's version-controlled alongside application code
• It expresses things env vars cannot: views, composite samplers, multiple exporters
• It supports ${VAR} substitution for secrets and environment-specific values

When to recommend declarative config

Recommend it when the user is setting up the OTel SDK for Go, Java, or JS. These SDKs have stable or near-stable implementations.