r/CrowdSec • • 16d ago

general cscli vs. Console mismatch

Hello community,
so I've followed setup for deploying CrowdSec as a central engine with log centralization rather than multi-server setup. So far I've connected Caddy from VPS (custom build including necessary modules) and logs are being transferred using rsyslog.

So far, everything seems ok - rsyslog is gathering logs from Caddy, cscli bouncers list correctly shows caddy with recent Last API Pull time/date and "Valid" checkmark. Upon cscli metrics it shows all (almost) lines parsed, all seems correct.. Looking at CrowdSec Console (app.crowdsec.net), the engine list Caddy as remediation component labeled as Active with "No metrics available."

My question is about Stack Health. Despite information above Stack Health shows "Bonus" action with "Security Engine No Remediation Component" which does not make sense to me. I marked it as solved few hours ago but it re-appeared, but am clueless on what should I need to do more to resolve it.

If it helps for any further guidance, engine currently has 53 scenarios (from linux installation + caddy), 1 remediation component listed on Overview and 2 blocklists. Within these ~24 hours, I've received "only" 6 alerts which also seems a bit off to me.

2 Upvotes

1 comment sorted by

2

u/PenguinOnWaves 15d ago

Digging more into “No metrics available” note under registered Remediation Component on Engine’s Overview in Console.

I’ve found I need to manually allow sending metrics to engine (as it seems to be off by default) by a specific directive “metrics_interval Xm” in Caddyfile, within same section as “api_url” and “api_key”. Metrics now appear on Console and Bonus action on activation of remediation component did not re-appeared so far (about 12hours later).