> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/mezmo-logdna.md).
# Mezmo (formerly LogDNA)
[Mezmo](https://www.mezmo.com/), formerly LogDNA, is an observability platform to manage and take action on your data.
Route detailed alerts from Postmark to the right users in Squadcast.
### Create a LogDNA service in Squadcast
1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.
2\. Select **LogDNA.** Copy the displayed **Webhook URL** to [configure](#setting-squadcast-webhooks-in-logdna) it within **LogDNA**. Finish by clicking **Add Alert Source** -> **Done.**
{% hint style="warning" %}
**Important:**
When an alert source turns Active, it’ll show up under Configured Alert Sources, you can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source. An Alert Source is active if there is a recorded incident via that Alert Source for the Service.
{% endhint %}
### Setting Squadcast webhooks in LogDNA
Login to your LogDNA account and navigate to the view for which you want to setup alerts.
On the View name, click on the dropdown and select **Attach an alert**.
Then select **View-Specific alert** from the drop down under **BUILD MY OWN** and click on **Webhooks**.
Then configure the type of alert and other conditions and enter Squadcast webhook url from the previous step in the **Webhook URL** text box and click on **Save Alert** button.
That's it! Your LogDNA integration is good to go and whenever the alert conditions are met, an incident will be automatically created in Squadcast.
*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*
---
# 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://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/mezmo-logdna.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.