WAF: AppsecRuntimeConfig log level is not properly set
When setting log_level: debug in an appsec-config (or directly in the acquisition), it looks like the log level is not properly set on the actual logger.
With a config like this and some additional debug in crowdsec:
source: appsec
log_level: trace
appsec_configs:
- crowdsecurity/virtual-patching
labels:
type: appsec
The log level seems to be set to panic:
INFO[2025-09-05T13:35:02+02:00] log level is panic request_uuid=ecdb0231-b68d-40cf-8ebc-f3cafca44fb4 runner_uuid=7f86723b-7a02-48bb-8f7c-3afffa6a2807 type=appsec
@blotus: Thanks for opening an issue, it is currently awaiting triage.
In the meantime, you can:
- Check Crowdsec Documentation to see if your issue can be self resolved.
- You can also join our Discord.
- Check Releases to make sure your agent is on the latest version.
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
@blotus: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
/kind feature/kind enhancement/kind refactoring/kind bug/kind packaging
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
/kind bug
will fix after https://github.com/crowdsecurity/crowdsec/pull/4045 and https://github.com/crowdsecurity/crowdsec/pull/4043