> 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/bleemeo.md). # Bleemeo Integration Create alerts in ilert from Bleemeo notifications — with ilert's Bleemeo inbound integration. [Bleemeo](https://bleemeo.com/) is a cloud monitoring platform for servers, containers, Kubernetes clusters, and websites. Its agent collects system metrics and its uptime monitors track availability; when a check crosses a warning or critical threshold, Bleemeo raises an incident and triggers the notification rules that match it. With this integration, a notification rule sends the incident to ilert as an event, ilert creates an alert, and your escalation policy decides who gets notified. ## In ilert: Create a Bleemeo alert source 1. Go to **Alerting** → **Alert sources** and click **Create new alert source**. 2. Search for **Bleemeo**, 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**.
The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below.

Pick an existing escalation policy, or generate a basic one without leaving the wizard.

5. Select your [event grouping](/alerting/configure-alerting/alert-sources.md#event-grouping) preference and click **Continue setup**. **Default grouping** is a good starting point, because Bleemeo sends an alert key that ilert uses to fold repeat events into the open alert. 6. The next page shows additional settings such as notification priority or affected services. Click **Finish setup** for now. 7. On the final page, ilert generates an **Integration key** and a **Bleemeo URL** for the alert source. Copy the integration key — Bleemeo needs it in the next section.
The settings tab of a Bleemeo alert source in ilert, with the integration key and Bleemeo URL fields outlined.
## In Bleemeo: Add the ilert integration 1. Click the **settings** icon at the bottom of the left sidebar.
The Bleemeo dashboard with the settings icon at the bottom of the left sidebar outlined.
2. Open the **Integrations** tab. It lists every integration configuration in the account, with a **Used by** column that shows how many notification rules reference each one.
The General tab of the Bleemeo account settings with the Integrations tab outlined in the top navigation.
3. Click the **+** button next to the **Integrations** heading.
The Bleemeo integrations list showing Discord, email, Microsoft Teams Workflows, mobile application, Rocket Chat, Telegram and webhook, with the plus button beside the Integrations heading outlined.
4. In **Add an integration configuration**, set **Integration Type** to **ilert** and give it an **Integration Name**. Use a name that says which alert source it points at — a Bleemeo account can hold several ilert configurations, one per alert source. 5. Paste the integration key you copied from ilert into **Integration key of your ilert Bleemeo alert source** and click **Save**.
The Add an integration configuration dialog in Bleemeo, with integration type ilert, the integration name field, and the masked integration key field outlined.
## FAQ #### **Will alerts in ilert be resolved automatically?** Yes. When the underlying problem clears in Bleemeo, Bleemeo sends a resolve event and ilert resolves the corresponding alert. #### **Will alerts in ilert be acknowledged automatically?** Yes. The alert source accepts acknowledge events, so an incident acknowledged in Bleemeo moves the matching alert in ilert to `ACCEPTED`. Accepting an alert stops escalation, because it means a human has taken ownership. --- # 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/bleemeo.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.