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

# Elecard Boro

[<mark style="color:blue;">Elecard Boro</mark>](https://www.elecard.com/products/quality-control/boro-service) is an IPTV monitoring software solution for UDP, RTP, HTTP, HLS and DASH streams quality control and measurement of QoS and QoE parameters in all segments of distributed networks.

Route detailed alerts from Elecard Boro to the right users in Squadcast.

### Using Elecard Boro as an Alert Source

1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.

![](/files/ej4AI9zpOyFu5NZJCbwC)

2\. Select **Elecard Boro**. Copy the displayed **Webhook URL** to [configure](#create-a-squadcast-webhook-notification-in-elecard-boro) it within **Elecard Boro**. Finish by clicking **Add Alert Source** -> **Done**.

![](/files/J5XkN29eW3E2IPFHbrMi)

{% hint style="warning" %} <mark style="color:orange;">**Important**</mark>**:**

When an alert source turns <mark style="color:green;">Active</mark>, 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 <mark style="color:green;">active</mark> if there is a recorded incident via that Alert Source for the Service.
{% endhint %}

### Create a Squadcast Webhook Notification in Elecard Boro

**(1)** Login to your Elecard Boro dashboard. Head over to the **MY PROJECTS** tab. Then, select the project of your choice

![](/files/f0tPzaEBwhMgPQT9UCUl)

**(2)** Click on **Project Settings**. Under the **Notifications** section, click on **WEBHOOK**

![](/files/5Bz9dZKJJJNm6ZU6Luhm)

**(3)** Under **WEBHOOK**, click on **Create profile**. Set the preferred **Language** and the **Timezone**. Enable the **Send error notifications via Webhook** and paste the previously copied Squadcast Webhook URL in the placeholder for **URL**

![](/files/aUumfXbmZMDqmoFWMVHx)

**(4)** Scroll down, set up your event triggers. Then click on **Save**

![](/files/f1c6g2Y9NXIucZpKtye0)

That's it, you are good to go! Your Elecard Boro integration is now complete. Whenever Elecard Boro fires an alert, an incident will be created in Squadcast for it. Also, when an alert has been **Cleared** in Elecard Boro, the corresponding incident gets **auto-resolved** 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/elecard_boro.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.
