← Directory

crowdsec-dashboard

Metabase dashboard template for displaying Crowdsec statistics.

  • Monitoring & Logging
  • Security
Metabase dashboard template for displaying Crowdsec statistics. MySQL and PostgreSQL are currently not supported, must use SQLite (default) as storage database with your local API.

Platform availability

Available on 3 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

88/100 Excellent

Maintained
100last commit 7 days ago
Popular
9449,556 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 16 days ago

GitHub stars
49,556
Open issues
4553
Last commit
2026-10-06
Latest release
v0.63.19
Activity
declining

Checked 7 days ago - source: GitHub (metabase/metabase)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 15 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Run interactive setup to detect log sources Run cscli setup interactive so CrowdSec finds your web servers, Secure Shell (SSH), and other services and writes the acquisition files for them. If you skip this, the dashboard has no logs to display because no log sources are configured. source
  • Set --acquis-dir and preview with --dry-run Set --acquis-dir to place acquisition files in your preferred directory, and use --dry-run first to preview what cscli setup install-acquisition will write. Skipping --dry-run can overwrite your custom log collector files. source
  • Install parser packs that match your services Install parser packs that match your log types, such as crowdsecurity/sshd-logs, so raw log lines become structured events. Without the right parsers, the dashboard may show unprocessed logs or miss detections. source

Fetched 15 days ago - each note links to its source

Alternatives (5)

  • Cloudflare - Protects websites with front-end proxy, dynamic DNS, CDN, and firewall; blocks DDoS and targeted attacks, optimizes traffic, and analyzes t…
  • CrowdSec - CrowdSec is a free, open-source and collaborative IPS.
  • Fail2ban - Fail2ban is a daemon that monitors log files and automatically bans hosts that cause multiple authentication failures, using firewall rules…
  • IPBanPro - IPBan is a FREE and open source application that allows auto banning ip addresses from failed login attempts.
  • defensia-agent

Checked yesterday - source: AlternativeTo

Common questions

How does cscli dashboard start Metabase when CrowdSec is running in Docker?

It tries to start Metabase in its own container.

Why does the dashboard show no logs after the initial CrowdSec setup?

Run cscli setup interactive so CrowdSec finds services and writes the acquisition files. If you skip it, no log sources are configured for the dashboard.

How can I avoid overwriting custom log collector files when installing acquisition files?

Set --acquis-dir to your preferred directory and run the acquisition install with --dry-run first. This lets you preview what will be written before it can overwrite custom files.

Answers sourced from doc.crowdsec.net, doc.crowdsec.net, www.reddit.com

Community

Collected 15 days ago - public community threads