Skip to content


Crowdsec configuration lives under /etc/crowdsec/config/ and should be as :


This is the 'main' configuration file, it allows to specify parameters such as :

  • logging (level and media)
  • directories (config, data, runtime)
  • API flag (on/off)
  • prometheus (on/off)
  • etc.

Default configuration

working_dir: /tmp/
data_dir: /var/lib/crowdsec/data
config_dir: /etc/crowdsec/config
pid_dir: /var/run
log_dir: /var/log/
log_mode: file
log_level: info
profiling: false
apimode: true
daemon: true
prometheus: true
#for prometheus agent / golang debugging
  backend: "/etc/crowdsec/plugins/backend"


The working directory where Prometheus will write metrics in text file.


Directory where Crowdsec will install its data (Crowdsec database for example).


To specify where Crowdsec PID file will be stored.


To specify where Crowdsec configuration will be stored.


To specify where the logs should be stored.


To specify your selected logging mode, available modes are :

  • file : to write logs in a file
  • stdout : to write logs in STDOUT


To specify the logging level, available levels:

  • debug
  • info
  • warning
  • error


To enable or disable the profiling in Crowdsec.


To enable or disable signals sending to the API.


To enable or disable Crowdsec daemon mode.


To enable or disable Prometheus metrics.


If prometheus is enabled, and is set to aggregated, will restrict prometheus metrics to global ones. All metrics containing a source as a label will be unregistered. Meant to keep cardinality low when relevant.


To configure the Prometheus service listening address:port or Crowdsec profiling


To specify the directories where output plugins will be stored : * backend: : the path where all Crowdsec backend plugins (database output, ...) will be located.


This is the file that tells which streams (or files) Crowdsec is reading, and their types (so that it knows how to parse them). If you're lucky, this file should be auto-generated by the wizard.

You can find details on the configuration file format here.


Name is self-explanatory : it holds API configuration.

This file should never be edited by a human : the wizard will deploy safe default for it, and cscli will alter it on your behalf when you register or enroll your machine.

You can look into it, and you should see :

  • url endpoints
  • login and password (auto-generated by your machine upon registration)

To get new credentials :

cscli api register

Or if you loose your credentials:

cscli api reset


The profiles is what allows you to decide how do you react when a scenario is triggered :

  • do you notify yourself on mattermost/slack ?
  • do you push the signal to a database so that your bouncers can stop the IP from continuing its attack ?
  • do you want to avoid pushing this signal to the API ?

Behind the scenes, the "profiles" system actually allows you to dispatch an event/overflow to various output plugins.

You can find details on the configuration file format of output.


This directory holds all the parsers that are enabled on your system.

The parsers are organized in stage (which are just folders) and the parsers themselves are yaml files.


This directory holds all the scenarios that are enabled on your system.

The scenarios are yaml files.