> 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/mezmo.md).

# Mezmo Integration

Receive Mezmo's alerts via phone calls, push notifications, SMS and other channels with the help of ilert

[Mezmo](https://www.mezmo.com/) is a log management and observability platform designed to centralize and analyze application logs in real-time. By integrating Mezmo with ilert, users can benefit from seamless alerting and incident response capabilities based on their log data. This integration allows users to set up automatic alerts within ilert for critical log events detected by Mezmo.

## In ilert: Create a Mezmo alert source <a href="#create-alarm-source" id="create-alarm-source"></a>

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Mezmo**, 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**.

   <figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-8a281bf3931f5a1a531951ce97984d50989dd875%2Falert-source-escalation-step.png?alt=media" alt="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."><figcaption><p>Pick an existing escalation policy, or generate a basic one without leaving the wizard.</p></figcaption></figure>
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.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FpIqNq7xjgHqea6GlCD77%2Fil-1.png?alt=media&amp;token=21675825-fd09-49c9-8518-d436892c77e9" alt="" width="563"><figcaption></figcaption></figure>

## In Mezmo: Create an alert Webhook

1. On the sidebar, click on the **Cog Wheel** icon.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fg6XSrvU1Ya6YqUc8gK0N%2F1.png?alt=media&amp;token=11d14836-087b-4ae8-98eb-ee117b64e17c" alt=""><figcaption></figcaption></figure>

2. Now click on **Alerts**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FNPrMQrfV0iG1EGUxKZBj%2F2.png?alt=media&amp;token=efc26036-ed29-44f2-b680-2100faaa8d52" alt="" width="293"><figcaption></figcaption></figure>

3. Click on **Add Preset**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FyMOch3HJUuIoW4Mh504X%2F3.png?alt=media&amp;token=8a57a6aa-96d7-4fc5-891e-feb378bd12b4" alt=""><figcaption></figcaption></figure>

4. Choose **Webhook**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FGeR6xquSD6tUgNHrYWxr%2F4.png?alt=media&amp;token=d8cda722-c5c2-4995-869a-35abe146be9a" alt=""><figcaption></figcaption></figure>

5. Enter a name for the webhook.
6. Change the **Method** to 'POST' and enter the alert source url previously generated in ilert into the URL field.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2F1Mv3WataP8BnSEXqI6W4%2F5.png?alt=media&amp;token=b52b608f-75d8-47a2-b4ad-4a4b953dab8f" alt=""><figcaption></figcaption></figure>

7. On the sidebar, click on the **Views** icon.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FWXcWXDPxSaEB9EXFuYWw%2F6.png?alt=media&amp;token=c6c419cd-f764-4572-bb4e-1752ef5c455b" alt=""><figcaption></figcaption></figure>

8. On your desired view, click on **Edit alert**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2F3mOlJ0bXiW2HFrRgJZQq%2F7.png?alt=media&amp;token=17967734-8d9a-47d9-9968-dd11b5015ab0" alt=""><figcaption></figcaption></figure>

9. Select the newly created webhook and save the alert.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FmkNoWnZIWdryhyLpS2fW%2F8.png?alt=media&amp;token=f3968019-09ff-4243-a630-5ba479715faa" alt=""><figcaption></figcaption></figure>

## FAQ

**Will alerts in ilert be resolved automatically?**

No, unfortunately Mezmo is not compatible with ilert's resolve event.


---

# 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/mezmo.md?ask=<question>&goal=<endgoal>
```

`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.
