Count the scenarios among recent CrowdSec alerts
Returns the scenarios among the newest 500 alerts that match since and kind, with how many of those alerts each one has, the most first. Scenarios with the same count sort by name. Answers 403 when the server has no CrowdSec machine credentials, CROWDSEC_MACHINE_ID and CROWDSEC_MACHINE_PASSWORD.
session<token>Session cookie authentication.
since?|Keep only alerts that started within this long before now, as a Go duration of hours, minutes and seconds such as 24h or 1h30m.
kind?|Keep only alerts of one kind, crowdsec, waf, bot-detection, capi, papi or cscli. bot keeps everything the AppSec bot challenge produces. Needs CrowdSec 1.7 or newer, and an older LAPI gets a 400.
Request fulfilled, document follows
application/json- response
[index: integer]?The number of decisions or alerts from one scenario.
curl -X GET 'https://geometrikks.example.com/api/v1/crowdsec/alerts/scenarios'[ { "count": 0, "scenario": "string" }]List CrowdSec alerts, newest first GET
Returns one page of the LAPI's alert history, newest first, without the community blocklist pulls. Pass the `nextCursor` of one page as `before` to get the next, older one. An IP source without a country from the LAPI gets its place from GeoMetrikks' own traffic, then from the GeoIP database. Answers 403 when the server has no CrowdSec machine credentials, CROWDSEC_MACHINE_ID and CROWDSEC_MACHINE_PASSWORD.
Get one CrowdSec alert GET
Returns the alert with its context, the events the LAPI kept and its decisions, expired ones included. Answers 403 when the server has no CrowdSec machine credentials, CROWDSEC_MACHINE_ID and CROWDSEC_MACHINE_PASSWORD.