Skip to main content
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.

In Flashduty On-call

You can get the 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 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, go to Integration Center → Alert Events
  2. Select LogRocket and enter an integration name
  3. Configure the default route and select a channel. You can add more rules under Routing after creation
  4. Click Save and copy the generated Push URL

Configure LogRocket

1

Create a webhook alert on a Timeseries chart in LogRocket

Where: LogRocket › Analytics › Timeseries › Alerts (top right of the chart) › Create AlertAlerts are only supported on saved Timeseries charts: build the chart and click Save first. Then click Alerts → Create Alert at the top right of the chart and fill in:Click Save Alert. An account can have up to 100 alerts, all managed on the Settings → Alerts page.
2

Push the metric past the threshold and confirm

Push the metric past the threshold. After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works. When the metric returns within the threshold, confirm the alert recovers automatically.
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

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

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
For more field details, see LogRocket metric alerts.