Skip to content
CrowdSec Local Dashboard

Changelog

All versionsAll versions forwardView on GitHub

Version v0.6.0-beta

Welcome to another release of CrowdSec Local Dashboard. This one makes alerts more useful, gives decision details a much better home, and adds a lot of polish across desktop and mobile. I hope you like it. Please let me know what you think and where it can improve.

Highlights

Alerts now explain what happened

The dashboard has always shown hosts and decisions. This release goes further by parsing the CrowdSec alert that produced each decision. A new integrations system turns source-specific alert data into readable evidence, so you can see details such as paths, ports, usernames, rules and request information instead of a generic row. The release includes integrations for AppSec, SSH, Traefik and OPNsense, with more sources to follow.

Parsed alert evidence in the dashboard

Stored alert data is kept and can be parsed again when a decision is opened, so parser improvements can make existing evidence more useful without fetching the alert from the Local API again.

Decision details have a proper home

Expanded decisions now open in a drawer instead of taking over a table row. The drawer gives the full alert context, parsed evidence, request metadata and timing information enough room on desktop, while making the same details much easier to inspect on a phone. Nothing important is hidden behind hover states or squeezed into a truncated row.

Decision details drawer on mobile

The first screenshot shows the new desktop layout. Be sure to visit the newly added documentation site too, which includes integration guides and a full overview of the dashboard. The README also has updated desktop and mobile screenshots.

Better tables on desktop and mobile

Tables now scroll independently while the toolbar and pagination stay available. Filters remain usable on narrow screens, touch devices can pull to refresh, and forms such as creating a user open in drawers when space is limited. The goal is to keep the same useful information available everywhere without making the interface feel cramped.

Clearer connection and offline states

The dashboard now distinguishes between being offline, being unable to reach the server, and an evidence request still loading or failing. It also ships with a proper offline page, a complete PWA manifest and mobile safe-area support.

Retention and performance improvements

Retention can now prune records by age as well as count, with an index added for the age-based query. Decision loading also avoids sending the same host data once per row, making larger tables less wasteful.

Upgrading

Download the compose file for this release, then pull and restart the container:

Terminal window
curl -o docker-compose.yml https://raw.githubusercontent.com/ollioddi/crowdsec-local-dashboard/main/docker-compose.yml
docker compose pull
docker compose up -d

The SQLite database lives in the db volume and survives updates. The container applies pending schema changes when it starts.

If you are upgrading from 0.5 or earlier, move your settings into a .env file beside docker-compose.yml. See the deployment guide for the details and for upgrades from older releases.

Breaking changes

There are no breaking changes for current 0.5.x installations. Older installations may need the configuration or database ownership steps described in the deployment guide.

Changes

Features

  • db: Store decision scope, simulation flag and alert timing (24a7b27)
  • retention: Prune by age as well as count, and index the query (#65, 37eb8f5)
  • table: Scroll the body, pin the toolbar and pagination (793bc66)
  • decisions: Confirm deletes, lead with evidence, tighten the rows (#66, 123be4a)
  • pwa: A complete manifest, an offline page and safe areas (88aaa9d)
  • table: Pull to refresh on touch (#67, a81bab6)
  • docs: Publish the docs as an Astro Starlight site (5666c4f)
  • db: Keep alert provenance and raw meta (16583e0)
  • parsing: Read alerts through integrations and facets (1258809)
  • sync: Store the raw alert and its provenance for the parsers (11b3b8f)
  • decisions: Re-parse the stored alert when a row is expanded (91e0c53)
  • ui: Rework the expanded decision row (16673f0)
  • ui: Open expanded cards as a sheet on phones (02c66d5)
  • ui: Keep filter chips to one row on phones (#82, 5554cf7)
  • sse: Send the heartbeat as an event (a9cf0be)
  • pwa: Register the worker in dev and leave the offline page by itself (e01cfd3)
  • ui: Say offline instead of live, and instead of fetch failed (d815417)
  • ui: Show a retry panel when the server cannot be reached (8783e71)
  • ui: Say the evidence is waiting or failed rather than missing (5821a27)

Bug fixes

  • lapi: Treat an already-removed decision as a successful delete (6a07009)
  • sync: Report alert fetch failures instead of swallowing them (#63, 632649f)
  • sync: Recover entries for alerts stored before extraction existed (#64, 97fb4ee)
  • ui: Restore pointer cursors, badge contrast and quiet scrollbars (7ed084c)
  • users: Put the create form in a drawer on narrow screens (#71, c4a1911)
  • table: Draw row separators as insets so Firefox keeps them (#73, b11168d)
  • ui: Stop one field swallowing the expanded row’s width (#74, 5edc0df)
  • theme: Follow the system scheme while it is selected (#76, a9b973e)
  • ui: Read the toaster theme from the app, not the OS (#79, 08dd1b0)

Performance

  • decisions: Send hosts as a lookup instead of once per row (3c972ca)

Documentation

  • changelog: V0.5.1-beta (#59) (#59, 0aa5c74)
  • readme: Keep the OIDC variables inside the configuration table (9fa8bec)
  • Move the setup guides out of the README into docs/ (810e647)
  • Describe the parsers and the reworked expanded row (#83, 6a14a56)
  • integrations: One page per source with desktop and phone captures (#84, c1bdc1d)
  • Describe offline behaviour and how to test it (#85, c23c10a)
  • Refresh release screenshots (#87) (#87, 02d0c58)

Dependencies

  • deps: Bump the actions group with 3 updates (#61, b81f9a2)

Full diff: v0.5.1-beta…v0.6.0-beta