Context
PR #468 hard-coded the max log level to Info in crates/fastly/src/main.rs:177 to prevent PII from leaking into production logs. This is the correct safe default, but the Fastly deploy model means toggling to Debug or Trace for incident response requires a code change and full redeploy.
Proposal
Add a config field (e.g. logging.max_level) that allows operators to control the log level without code changes. This would be useful for controlled incident response and staging debugging while keeping Info as the safe default.
References
Context
PR #468 hard-coded the max log level to
Infoincrates/fastly/src/main.rs:177to prevent PII from leaking into production logs. This is the correct safe default, but the Fastly deploy model means toggling toDebugorTracefor incident response requires a code change and full redeploy.Proposal
Add a config field (e.g.
logging.max_level) that allows operators to control the log level without code changes. This would be useful for controlled incident response and staging debugging while keepingInfoas the safe default.References