Alerts & Grafana

Open Alerts

Select a project in the panel and choose Alerts from the left menu. The page has three tabs:

The Destinations tab opens first. Create and enable at least one destination before adding a rule. Admins can create, edit, test, enable, and delete configurations; other project users can view the page.

Connect Grafana Cloud IRM

1. In Grafana Cloud IRM, open Integrations → Monitoring systems, create a Formatted Webhook integration, and copy its webhook URL. Grafana's OnCall incoming webhook guide has the current Grafana steps.
2. In LogDrop, open Alerts → Destinations and select New destination.
3. Enter a Name, choose Grafana Cloud IRM as the Destination type, and paste the URL into Webhook URL.
4. If the Grafana integration requires a service account token, enter the full Bearer <token> value in Authorization header (optional).
5. Set Destination cooldown, leave Enabled on, and select Test connection. Then select Save.

Screenshot: New destination

The destination type defaults to Email in this screenshot. Select Grafana Cloud IRM to show the webhook URL and optional authorization fields.

The Destinations table shows the masked URL, whether authorization is configured, and the last test result. You can also use Test on a saved destination. A connection test sends a test message to Grafana; it does not create an alert occurrence or change rule counters.

When editing a destination, leave the URL or authorization field blank to keep its stored value. The editor also has Remove stored authorization header if you need to clear the token. LogDrop stores the URL and authorization header encrypted.

LogDrop sends Grafana Cloud IRM a formatted payload with an alert ID, title, alerting state, summary, and a link back to LogDrop. It currently sends the firing state only; it does not send a later ok event to resolve the Grafana alert automatically.

Create a rule

1. Open Alerts → Rules and select New rule.
2. Enter a Name and choose a Signal source. Add one or more Matching conditions using a field, operator, and value. All conditions must match the same signal.
3. Set Event threshold and Window (seconds). For example, a threshold of 3 in a window of 300 fires after three matching signals within five minutes.
4. Optionally set Distinct devices and Rule cooldown (seconds). A distinct-device threshold cannot exceed the event threshold.
5. Select one or more enabled Destinations, keep Enabled on, and select Save.

Screenshot: New rule

For an event property, choose Event property and enter its property name. Enter multiple values separated by commas where the selected operator permits them. Numeric fields use numeric values; boolean fields use true or false.

Before saving, use Matching preview: paste a sample JSON signal and select Test match. The result tells you whether the sample matches the rule's conditions. It does not send an alert or evaluate the threshold over time.

The Rules tab shows each rule's condition summary, policy, destinations, latest trigger, match count, and trigger count. An admin can use the switch to disable a rule, or edit or delete it from the row.

Review alert history

Open Alerts → History to see occurrences and each destination's delivery status. Filter by Pending, Sent, Suppressed, or Failed; use Refresh for new results and Previous or Next to move through pages. The link at the end of a row opens the related LogDrop data.

Suppressed can indicate a rule or destination cooldown. If a Grafana delivery fails, first check the destination's test result and webhook URL, then inspect the occurrence's delivery status in History. Remove a destination from every rule before deleting it.

Other destination types

The same rule can send to several destinations. In New destination, choose Email (comma-separated addresses), Slack (incoming webhook URL), Webhook (public URL), or Alertmanager (alerts endpoint URL). Webhook destinations can also use an optional Authorization header. Choose the destination type that matches the receiver's payload format.