> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LogRocket alert integration

> Send LogRocket Timeseries chart alerts to Flashduty On-call through a webhook.

Use the Webhook alert type of a LogRocket Timeseries chart to send metric alerts to Flashduty On-call. Each LogRocket alert maps to one Flashduty alert: it triggers when the metric crosses the threshold and recovers automatically when the metric returns within it.

<div className="hide">
  ## In Flashduty On-call

  ***

  You can obtain an integration push URL in either of the following ways.

  ### Use a dedicated integration

  1. In the Flashduty console, select **Channel** and open a channel
  2. Select **Configuration** → **Integrations** → **Private integration**, then click **Add an integration**
  3. Select **LogRocket**, then click **Save**
  4. Open the generated integration card and copy the **Push URL**

  ### Use a shared integration

  1. In the Flashduty console, select **Integration Center → Alert Events**
  2. Select **LogRocket** and enter an integration name
  3. Configure the default route and select a channel; after creation, add more rules under **Route** if needed
  4. Click **Save** and copy the generated **Push URL**
</div>

## Configure LogRocket

***

<Steps>
  <Step title="Add a Webhook alert to a Timeseries chart">
    1. In LogRocket, open **Analytics → Timeseries**, build the chart you want to alert on, and click **Save** (alerts are supported only on saved Timeseries charts)
    2. Click **Alerts → Create Alert** at the top right of the chart, and enter an **Alert name**
    3. Under **Trigger alert when**, set the comparison (**greater than** or **less than**), the threshold, and the time window, for example "Session count is less than 1 sessions within 5 minutes"
    4. Under **Send alert via**, select **Webhook**, paste the full Flashduty push URL, including `integration_key`, into the **Webhook** field, and click **Save Alert**

    An account can have up to 100 alerts, all managed on the **Alerts** page in Settings.
  </Step>

  <Step title="Verify">
    Push the metric past the threshold and confirm Flashduty receives an active alert; when the metric returns within the threshold, confirm the alert recovers automatically.
  </Step>
</Steps>

The Issues Alerts webhook (new severe issues) uses a different message format and carries no alert ID, so it cannot be tied to a recovery. Flashduty acknowledges it and creates no alert.

## Alert Key

***

The Alert Key is the `alert_id` LogRocket sends. LogRocket documents that this ID stays the same across multiple triggerings and resolutions of the same alert, so the trigger and recovery events share one Alert Key. Editing the alert's threshold, interval, or chart location does not change it. Requests without `alert_id` are rejected.

## Status and severity

***

| LogRocket `status` | Flashduty status | Flashduty severity |
| :- | :- | :- |
| `triggered` | Triggered | Warning |
| `resolved` | Recovered | - |

The LogRocket webhook carries no severity, and a metric crossing a threshold is not the same as an outage, so every alert is Warning. Any other `status` value is rejected.

## Labels

***

| Label | Source |
| :- | :- |
| `alert_id` | LogRocket alert ID |
| `status` | `triggered` or `resolved` |
| `check` | Alert title, taken from `reason` |
| `project_url` | Link to the LogRocket project |
| `dashboard_url` | Link to the dashboard containing the chart |
| `metric_url` | Link to the chart |
| `operator` | Comparison, `GT` or `LT` |
| `threshold` / `threshold_unit` | Threshold and its unit |
| `interval` / `interval_unit` | Evaluation interval and its unit (`MINUTES` or `HOURS`) |

The alert title and description come from `reason`, which LogRocket fills with the alert name you entered. Without `reason` the title is `LogRocket alert <alert_id>`.

## Troubleshooting

***

* **Flashduty returns an invalid parameter error**: check that the URL is complete and includes `integration_key`, and that the request comes from a Timeseries chart alert rather than Issues Alerts
* **The alert does not recover**: check that the resolved notification is sent to the same URL and that its `alert_id` matches the one sent on trigger
* **The alert stays open for a long time**: turn on the channel's auto-close timeout as a fallback for a lost resolved notification; see [Create a channel](/en/on-call/channel/create-edit)

For more field details, see [LogRocket metric alerts](https://docs.logrocket.com/docs/metrics-alerting).