blotus
blotus
Hello, We need to document the internal workings of the metrics system in LAPI to facilitate the implementation for third-party bouncers. The gist of it: - The metrics shown in...
Hello, We are reworking the way we collect metrics / add more metrics in this PR: https://github.com/crowdsecurity/cs-firewall-bouncer/pull/365 (the goal is to provide those metrics as well in `cscli metrics`, and...
Hello, I've just merged #365, and it should be released this week. There are some significant changes in how we collect metrics: - Reduced ticker usage: metrics are now only...
Hello, Sorry for the confusion, but at the moment TLS authentication between a bouncer and the appsec datasource is not supported. This is quite tricky to implement: by default, we...
Hello, Was there a log rotation or something else around the time the decision was taken ? The only thing I can think of right now is an issue during...
Hello, Unless I'm mistaken, this effectively allowlist *all* the AWS IPs ? (including EC2). While allowing cloudfront is probably a good idea, allowing any EC2 IP seems kinda dangerous: even...
Hello, It is indeed an oversight. In the meantime, you can use `profiles.yaml` to mount a custom profile configuration (this will replace the default profile file, so you'll probably want...
Hello, The bouncer should run as a separate deployment. At the time, we do not have a chart for it, but you can use a deployment that looks like this:...
Hello, The parser provided in crowdsec only supports the default W3C format (which does not include the service name or the server name). If your logs use those fields, you...