Agent fails to parse logs - but cscli explain works

joaogbcravo · January 26, 2023, 1:42pm

For future travelers, if you are running on kubernetes and your runtime is not docker, you need to setup the correct type here. In my case was containerd.

If you are using helm, make sure to override this variable on your values.yaml.

github.com

crowdsecurity/helm-charts/blob/20f64df00a413e037ee2ca63afd9e9dc7ee9b393/charts/crowdsec/values.yaml#L8


      
          # yaml-language-server: $schema=https://raw.githubusercontent.com/crowdsecurity/helm-charts/main/charts/crowdsec/values.schema.json
          
          # Default values for crowdsec-chart.
          # This is a YAML-formatted file.
          # Declare variables to be passed into your templates.
          
          # -- for raw logs format: json or cri (docker|containerd)
          container_runtime: docker
          
          image:
            # -- docker image repository name
            repository: crowdsecurity/crowdsec
            # -- pullPolicy
            pullPolicy: IfNotPresent
            # -- docker image tag
            tag: ""
          
          # Here you can specify your own custom configuration to be loaded in crowdsec agent or lapi

Topic		Replies	Views
Nginx logs not being parsed - cscli explain works crowdsec	1	1137	January 31, 2023
Ingress Nginx parse file on One agent crowdsec	2	340	November 2, 2023
Nginx logs not being parsed	6	1542	September 15, 2021
Solution for parsing logs of docker containers crowdsec	5	4841	July 30, 2022
Crowdsec failing to start after executing cscli explain crowdsec	2	2025	May 25, 2022

Agent fails to parse logs - but cscli explain works

Related topics