The command cscli metrics queries the Prometheus metrics exposed locally by CrowdSec and presents them in a fancy terminal output: | crowdsecurity/geoip-enrich | 2 | 2 | - | | crowdsecurity/dateparse-enrich | 2 | 2 | - | | child-crowdsecurity/nginx-logs | 2 | 2 | - | | child-crowdsecurity/http-logs | 6 | 2 | 4 | | SOURCE | LINES READ | LINES PARSED | LINES UNPARSED | LINES POURED TO BUCKET | | crowdsecurity/http-crawl-non_statics | - | - | 2 | 2 | 2 | | BUCKET | CURRENT COUNT | OVERFLOWS | INSTANCIATED | POURED | EXPIRED |+-+-+-+-+-+-+ ▶ sudo docker-compose exec crowdsec cscli metrics We have put the configuration files altogether on this repository, so that you can simply clone it to deploy.įrom the Docker Compose directory, you can deploy with docker-compose up -d and then check that everything is running with docker-compose ps. The reverse-proxy (nginx) container writes its logs to a logs volume mounted by the crowdsec container.ĬrowdSec's SQLite database is in a crowdsec-db volume mounted by the dashboard (metabase) container Initial deployment #we're using a custom Dockerfile so that metabase pops with pre-configured dashboards #metabase, because security is cool, but dashboards are cooler crowdsec/acquis.yaml:/etc/crowdsec/acquis.yaml #METABASE ALERTS INSTALL##this is the list of collections we want to install #and later we're going to plug a firewall bouncer to it #the reverse proxy that will serve the application If you need any additional information on our API, please don’t hesitate to contact us at info hyperswell.#the application itself : static html served by apache2. To enable it please switch the toggle on in the top right corner. By default, your alert is in the disabled status. Once you created an alert, you will be redirected to its page. Now, configure the frequency by choosing one of the options.Īnd this is almost it! When you’re done with all the settings, click on the “Save” button and give the alert a name. Please note that you can deliver notifications to both private and public channels. At any point, you can preview the results by clicking the “Play” button on the bottom left corner of the SQL editor.īelow, enter your notification – an alert that will be delivered to a selected slack channel (please, select one of your slack channels in the dropdown field below). Next, type your SQL query in the SQL area below. On the New Alert creation page, select Metabase in the “Data source for alert” field. From any page click the “New alert” button located at the top right corner. Now you can create an alert and set automation. If you need more information or help to connect or configure your account, read our step-by-step docs at our help center. If necessary, log in to your Metabase account at and give HyperSwell permission to access your Metabase account. Then fill in all the required fields and click Continue. Go to HyperSwell Dashboard and in the list of Data Sources click the “Add a Database” link.Īt the top of the next page select Metabase in the “Data source type” dropdown. The very first thing you need to do is to connect your Metabase account. From the Dashboard click the “Connect my Slack” button and allow HyperSwell to access your Slack workspace. If that’s a new HyperSwell account and/or you haven’t done this yet, first of all, go ahead and connect your Slack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |