---
title: "Connect SigNoz"
description: "Send SigNoz alerts to Firefight through a Webhook notification channel."
canonical: https://firefight.app/docs/alerts/signoz
---

# Connect SigNoz

Firefight has a dedicated alert source for SigNoz. SigNoz sends a group of alerts in each request, and Firefight turns each one into its own alert that resolves when SigNoz resolves it.

## Set up the Firefight side

Go to **Settings → Alert Sources**, click **Add source**, give it a name like "SigNoz production", and pick the **SigNoz** provider. When you create it, Firefight opens the source's setup. It shows the ingest URL and a **Copy token** button for the source's secret token, and the same steps as this page.

## Set up the SigNoz side

1. In SigNoz, open **Settings → Notification Channels** and click **New Channel**. Choose the **Webhook** type.
2. Paste the ingest URL as the **Webhook URL**.
3. Leave **Username** empty and paste the token as the **Password**.
4. Leave **Send resolved alerts** on, click **Test**, save, and choose the channel in your alert rules.

Requests that fail the check are rejected with `401`, and the source's row in **Settings → Alert Sources** shows the rejection.

## What Firefight reads

Each alert gets these fields, which you can match in your [routing rules](https://firefight.app/docs/alerts/routing-rules.md).

| Field | Value |
|---|---|
| `title` | The `alertname` label |
| `description` | The `summary` and `description` annotations |
| `service` | The `service` label, else `job` |
| `severity_raw` | The `severity` label |
| `team` | The `team` label |
| `environment` | The `environment` label, else `env` |
| `url` | The alert rule in SigNoz |

The alert's title in Slack and on the dashboard links to its page in SigNoz.

## Firing and resolving

Each alert in the group is its own alert in Firefight, identified by its fingerprint. A repeat notification counts on the same alert, and a resolved notification resolves it.

See [Grouping & deduplication](https://firefight.app/docs/alerts/grouping-and-deduplication.md) for how repeat firings collapse into one alert.