> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/humio.md).
# CrowdStrike Falcon LogScale Integration
Send CrowdStrike Falcon LogScale's (previously, Humio) log-based alerts to ilert to notify on-call teams of critical log events and trigger structured incident escalation.
[CrowdStrike Falcon LogScale](https://www.crowdstrike.com/en-us/platform/next-gen-siem/falcon-logscale/) provides logging and observability service that gives organizations complete visibility to see anomalies, threats, and problems, and get to the root of what happened. With CrowdStrike Falcon LogScale integrated, log-based alerts – such as threshold breaches or anomaly detections – are forwarded to on-call responders via ilert. These alerts activate escalation paths and provide engineers with essential context to resolve issues quickly and confidently.
{% hint style="info" %}
Humio has been renamed to CrowdStrike Falcon LogScale
{% endhint %}
## In ilert: Create a CrowdStrike Falcon LogScale alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **CrowdStrike LogScale**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In CrowdStrike Falcon LogScale
1. Create an Action by clicking **Alerts** -> **Actions** -> **New Action** from your dashboard
2. Choose **Webhook** as type, fill in the name in this case **ilert-webhook**, and on Endpoint URL, put on the **Humio URL** that is generated on ilert
3. Save the Action Webhook by clicking on **Save Action** after scrolling down
4. Add a new Alert by Clicking **Alerts -> Alerts -> New Alert**
5. Create the Alert by specifying the query that you want the Alert to be based on, and don't forget to check **Alert Enabled** and put the **Webhook Action** that has been configured earlier
6. Save the alert, and upon the alert, the incident will be created on ilert side as well
7. For more information about LogScale Alerts please refer to the following:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/integrations/inbound-integrations/humio.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
