# Lightstep Integration

[Lightstep](https://docs.lightstep.com/) automatically detects changes to your application, infrastructure, and user experience to provide better monitoring and observability. By sending Lightstep tracing alerts into ilert, your on-call engineers receive timely technical alerts about service latency, error spikes, or performance anomalies. Automated escalation ensures issues are addressed quickly before they impact end users or SLAs.

{% hint style="warning" %}
Cloud Observability / Lightstep will no longer be supported after March 1, 2026. For details and migration guidance, see [the official documentation](https://docs.lightstep.com/changelog/eol-notice).
{% endhint %}

## In ilert: Create a Lightstep alert source

1. Go to **Alert sources** --> **Alert sources** and click on **Create new alert source**

   <figure><img src="/files/rmL9OoRxcWnDwcJZQm4Y" alt=""><figcaption></figcaption></figure>
2. Search for **Lightstep** in the search field, click on the Lightstep tile and click on **Next**.

   <figure><img src="/files/1WoRRYB5U40PbeMJ7Hit" alt=""><figcaption></figcaption></figure>
3. Give your alert source a name, optionally assign teams and click **Next**.
4. Select an **escalation policy** by creating a new one or assigning an existing one.

   <figure><img src="/files/y4Bakf2apGhBN56U8ZPR" alt=""><figcaption></figcaption></figure>
5. Select you [Alert grouping](/alerting/configure-alerting/alert-sources.md#alert-grouping) preference and click **Continue setup**. You may click **Do not group alerts** for now and change it later.

   <figure><img src="/files/nTlB0ZCIW1SP3dj6P9nO" alt=""><figcaption></figcaption></figure>
6. The next page show additional settings such as customer alert templates or notification prioritiy. Click on **Finish setup** for now.
7. On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.

   <figure><img src="/files/iFF3BpyuIYMi49K1j7uk" alt=""><figcaption></figcaption></figure>

## In Lightstep

1. Create a **Notification Destination** by clicking the **Bell Icon** on the left of Dashboard, and click "**Notification Destination**" tab and click "**Create a Destination**" and choose "**Webhook**"

![](/files/V8UwlYgKfMieKH8ix0fP)

2. Complete the webhook creation, by putting in the name and put the **Lighstep URL** that we got earlier in ilert dashboard on URL field

![](/files/vGy72qNq4d0A0EAGuFU8)

3. You need to assign the webhook destination to an Alert, if you don't have an Alert, you can create a new one, by navigating to Stream (**Frequency Wave icon** on the left side of the dashboad) and click the stream that you want to assign to

![](/files/htxmbvhBPJ7558NnyQRI)

4. **Create an alert** by clicking the button on the top right of the stream dashboard, fill in the details, and assign the **Notifcation** **Destination** to the one that we created earlier

![](/files/l6qAcfULExz0uCS8Wht8)

5. Upon clicking "**Create**" button, the alert should be created and the Notification Destination should be assigned, and when the condition met, it will create an incident on ilert

![](/files/eZAKLm5ERUd1Y3cf0bmi)


---

# Agent Instructions: 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:

```
GET https://docs.ilert.com/integrations/inbound-integrations/lightstep.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
