CrowdSec Dashboard

Metabase dashboard template for displaying Crowdsec statistics.

  • Databases
  • Monitoring & Logging
  • Other
  • Security
  • Tools & Utilities
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 4 of 10 platforms

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

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 22 days ago
Popular
9450,022 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM

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

GitHub stars
50,022
Open issues
4650
Last commit
2026-10-30
Latest release
v0.65.2
Activity
rising

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

Resources & Compatibility

Minimum requirements: 1 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 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 54 days ago - each note links to its source

Alternatives (6)

  • Grafana - Grafana is an open-source monitoring and observability platform for querying, visualizing, alerting on, and sharing dashboards for metrics…
  • Looker Studio - Data visualization and business intelligence (BI) platform for aggregating, sharing, collaborating, and pulling insights from raw databases…
  • Microsoft Power BI - Enhance your decision-making by transforming diverse data sources into engaging, interactive visual insights with tools like Power BI Deskt…
  • Tableau - Tableau helps the world’s largest organizations unleash the power of their most valuable assets: their data and their people.
  • apache-superset - Apache Superset is a modern data exploration and visualization platform.
  • redash - Redash is a browser-based business intelligence (BI) tool for exploring, querying, visualizing, and sharing data from any data source.

Checked 40 days ago - 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 48 days ago - public community threads