Thibault "bui" Koechlin
Thibault "bui" Koechlin
Currently, the docker documentation isn't very clear about running "Log Processor" or "LAPI" only. The documentation is speaking about agent (?). A quick iteration could help improve this significantly.
- How to add metrics to a bouncer - What kind of metrics should be sent - The format of the metrics
- add `sigmahq` auditd rules - update the auditd and laurel parsers, reflect changes on associated scenarios
After 1.6.5 and the registration token, we should enable the flush by default to avoid over consumption of slots in the console. (see. https://github.com/crowdsecurity/crowdsec-docs/issues/730)
### What would you like to be added? ## Indicate the user if nginx isn't running If one forgot to start the docker-compose to have nginx running, the error message...
### What would you like to be added? Currently, when a user upgrades its SaaS plan, he needs to take several steps to take advantage of it: - enable `console_management`...
### What happened? Having something like: ```yaml name: smth/rules log_level: trace default_remediation: ban inband_rules: - smth/rules ``` With `smth/rules` being: ```yaml name: smth/rules seclang_rules: - SecRuleEngine On - SecRequestBodyAccess On...
And also the 5 other missing ones ❤️
## Description ## Checklist - [ ] I have read the [contributing guide](https://docs.crowdsec.net/docs/next/contributing/contributing_hub) - [ ] I have tested my changes locally - [ ] For new parsers or scenarios,...